View XRT94L33IB_3413777.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

xr xrt94l33 3-channel ds3/e3/sts-1 to sts- 3/stm-1 mapper ic data sheet e corporation 48720 kato road, fremont ca, 94538 * (510) 668-7000 * fax (510) 668-7017 * www.exar.com n0vember 2006 rev.1.2.0. general description the xrt94l33 is a highly integrated sonet/sdh terminator designed for e3/ds3/sts-1 mapping/de-mapping functions from either the sts-3 or stm-1 data stream. the xrt94l33 interfaces directly to the optical transceiver the xrt94l33 processes the section, line and path overhead in the sonet/sdh data stream and also performs atm and ppp phy-layer processing. the processing of path overhead bytes within the sts-1s or tug-3s includes 64 bytes for storing the j1 bytes. path overhead bytes can be accessed through the microp rocessor interface or via serial interface. the xrt94l33 uses the internal e3/ds3 de- synchronizer circuit with an internal pointer leak algorithm for clock smoothing as well as to remove the jitter due to mapping and pointer movements. these de-synchronizer circuits do not need any external clock reference for its operation. the sonet/sdh transmit blocks allow flexible insertion of toh and poh bytes through both hardware and software. individual poh bytes for the transmitted sonet/sdh signal are mapped either from the xrt94l33 memory map or from external interface. a1, a2 framing pattern, c1 byte and h1, h2 pointer byte are generated. the sonet/sdh receive blocks receive sonet sts-3 signal or sdh stm-1 signal and perform the necessary transport and path overhead processing. the xrt94l33 provides a line side aps (automatic protection switching) interface by offering redundant receive serial interface to be switched at the frame boundary. the xrt94l33 provides 3 mappers for performing sts-1/vc-3 to sts-1/ds3/e3 mapping function, one for each sts-1/ds3/e3 framers. a prbs test pattern generation and detection is implemented to measure the bit-error performance. a general-purpose microprocessor interface is included for control, configuration and monitoring. applications ? network switches ? add/drop multiplexer ? w-dcs digital cross connect systems features ? provides ds3/ e3 mapping/de-mapping for up to 3 tributaries through sonet sts-1 or sdh au- 3 and/or tug-3/au-4 containers ? generates and terminates sonet/sdh section, line and path layers ? integrated serdes with clock recovery circuit ? provides sonet frame scrambling and descrambling ? integrated clock synthesi zer that generates 155 mhz and 77.76 mhz clock from an external 12.96/19.44/77.76 mhz reference clock ? integrated 3 e3/ds3/sts-1 de-synchronizer circuit that de-jitter gapped clock to meet 0.05uipp jitter requirements ? access to line or section dcc ? level 2 performance monitoring for e3 and ds3 ? supports mixing of sts-1e and ds3 or e3 and ds3 tributaries ? utopia level 2 interface for atm or level 2p for packets ? e3 and ds3 framers for both transmit and receive directions ? complete transport/section overhead processing and generation per telcordia and itu standards ? single phy and multi-phy operations supported ? full line aps support for redundancy applications ? loopback support for both sonet/sdh as well as e3/ds3/sts-1 ? boundary scan capability with jtag ieee 1149 ? 8-bit microprocessor interface ? 3.3 v 5% power supply; 5 v input signal tolerance ? -40c to +85c operating temperature range ? available in a 504 ball tbga package
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 2 block diagram of the xrt94l33 telecom bus interface oc3 txrx sonet/sdh toh sonet/sdh poh sdh mux sonet/sdh poh utopia ii/iip interface telecom bus interface telecom bus interface telecom bus interface sonet/sdh poh sonet/sdh poh boundry scan microprocessor interface to ds3/e3 sts-1 telecom bus/ t3/e3/hdlc intf to ds3/e3 sts-1 telecom bus/ t3/e3/hdlc intf to ds3/e3 sts-1 telecom bus/ t3/e3/hdlc intf to oc12 to f.o. sts-1 channel 2 ds3/e3 mapper pointer justify sts-1 tx/rx toh & poh jitter attenuator & clock smoothing ds3/e3 framer hdlc controller plcp ppp processor atm processor sts-1 channel 1 ds3/e3 mapper pointer justify sts-1 tx/rx toh & poh jitter attenuator & clock smoothing ds3/e3 framer hdlc controller plcp ppp processor atm processor sts-1 channel 0 ds3/e3 mapper pointer justify sts-1 tx/rx toh & poh jitter attenuator & clock smoothing ds3/e3 framer hdlc controller plcp ppp processor atm processor ordering information p art n umber p ackage t ype o perating t emperature r ange XRT94L33IB 27 x 27 504 lead tbga -40c to +85c
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 3 pin description of the xrt94l33 (rev. b) p in # s ignal n ame i/o s ignal t ype d escription m icroprocessor i nterface y22 pclk i ttl microprocessor inte rface clock input: this clock input signal is only used if the microprocessor interface has been configured to operate in one of the synchronous mode (e.g., power pc 403 mode). if the microprocessor interface is configur ed to operate in one of these modes, then it will use this clock signal to do the following. ? to sample the cs*, wr*/r/w*, a[14:0], d[7:0], rd*/ds* and dben input pins, and ? to update the state of d[ 7:0] and the rdy/dtack output signals. notes: 1. the microprocessor interface can work with pclk frequencies ranging up to 33mhz. 2. this pin is inactive if the user has configured the microprocessor interface to operate in either the intel- asynchronous or the motorola-asynchronousl modes. in this case, the user shou ld tie this pin to gnd. ad25 ad23 ac21 ptype_0 ptype_1 ptype_2 i ttl microprocessor type select input: these three input pins permit the user to configure the microprocessor interface block to readily support a wide variety of microprocessor interfaces. the relationship between the settings of these input pins and the corresponding microprocessor interface confi guration is presented below. ptype[2:0] microprocessor interface mode 000 intel-asynchronous mode 001 motorola ? asynchronous mode 010 intel x86 011 intel i960 100 idt3051/52 (mips) 101 power pc 403 mode 111 motorola 860
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 4 p in # s ignal n ame i/o s ignal t ype d escription ad27 ab25 w23 y24 ad26 ac25 aa24 y23 ae24 ab20 ad22 ac20 ad21 ae23 af24 paddr_0 paddr_1 paddr_2 paddr_3 paddr_4 paddr_5 paddr_6 paddr_7 paddr_8 paddr_9 paddr_10 paddr_11 paddr_12 paddr_13 paddr_14 i ttl address bus input pins (microprocessor interface): these pins permit the microprocessor to identify on-chip registers and buffer/memory locations (within the xrt94l33) whenever it performs read and write operations with the xrt94l33. ad20 ac19 ae22 ag24 ae21 ad19 af23 ae20 pdata_0 pdata_1 pdata_2 pdata_3 pdata_4 pdata_5 pdata_6 pdata_7 i/o ttl bi-directional data bus pins (microprocessor interface): these pins are used to drive and receive data over the bi- directional data bus, whenever the microprocessor performs read and write operations with the microprocessor interface of the xrt94l33.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 5 p in # s ignal n ame i/o s ignal t ype d escription af22 pwr_l/ r/w* i ttl write strobe/read-write operation identifier: the exact function of this input pin depends upon which mode the microprocessor interface has been configured to operate in, as described below. intel-asynchronous mode ? wr* - write strobe input: if the microprocessor interface is configured to operate in the intel-asynchronous mode, then this input pin functions as the wr* (active-low write strobe) input signal from the microprocessor. once this active-l ow signal is a sserted, then the input buffers (associated with the bi-directional data bus pins, d[7:0]) will be enabled. the microprocessor interface will latch the contents on the bi-directi onal data bus (into the ?target? register or address location, within the xrt94l33) upon the rising of this input. motorola-asynchronous mode - r/w* - read/write operation identification input pin: if the microprocessor interface is operating in the ?motorola- asynchronous? mode, then this pin is functionally equivalent to the ?r/w*? input pin. in the motorola mode, a ?read? operation occurs if this pin is held at a logic ?1?, coincident to a falling edge of the rd/ds* (data st robe) input pin. powerpc 403 mode ? r/w* - read/write operation identification input: if the microprocessor interface is configured to operate in the powerpc 403 mode, then this input pin will function as the ?read/write operation identification? input pin. anytime the microprocessor interface samples this input signal at a logic ?low? (while also sampling the cs* input pin ?low?) upon the rising edge of pclk, then the microprocessor interface will (upon the very same rising edge of pclk) latch the contents of the address bus (a]14:0]) into the microprocessor interface circuitry, in preparation for this forthcoming read operation. at some point (later in this read operation) the microprocessor will also assert the dben*/oe* input pin, and the microprocessor interface will then place the content s of the ?target? register (or address location within the xrt94l33) upon the bi-directional dat bus pins (d[7:0]), where it can be read by the microprocessor. anytime the microprocessor interface samples this input signal at a logic high (while also sampling the cs* input pin at a logic ?low?) upon the rising edge of pclk, then the microprocessor interface will (upon the very same rising edge of pclk) latch the contents of the address bus (a[ 14:0]) into the microprocessor interface circuitry, in preparation for the forthcoming write operation. at some point (later in this write operation) the microprocessor will also assert the rd*/ds*/we* input pin, and the microprocessor interface will then latch the contents of the bi-directional data bus (d[7:0]) into the contents of the ?target? register or buffer location (within the xrt94l33).
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 6 p in # s ignal n ame i/o s ignal t ype d escription ac18 prd_l/ ds*/ we* i ttl read strobe /data strobe: the exact function of this input pin depends upon which mode the microprocessor interface has been configured to operate in, as described below. intel-asynchronous mode ? rd* - read strobe input: if the microprocessor interface is operating in the intel- asynchronous mode, then this input pin will function as the rd* (active low read strobe) input signal from the microprocessor. once this active-low signal is asserted, then the xrt94l33 will place the contents of the addresse d register (or buffer location) on the microprocessor bi-directional data bus (d[7:0]). when this signal is negated, the data bus will be tri-stated. motorola-asynchronous (68k) mode ? ds* - data strobe input: if the microprocessor interface is operating in the motorola asynchronous mode, then this input will function as the ds* (data strobe) input signal. powerpc 403 mode ? we* - write enable input: if the microprocessor interface is operating in the powerpc 403 mode, then this input pin will f unction as the we* (write enable) input pin. anytime the microprocessor interface samples this active-low input signal (along with cs* and wr*/r/w*) also being asserted (at a logic level) upon the rising edge of pclk, then the microprocessor interface will (upon the very same rising edge of pclk) latch the contents on the bi-directional data bus (d[7:0]) into the ?target? on-chip register or buffer location within the xrt94l33.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 7 p in # s ignal n ame i/o s ignal t ype d escription ag23 ale/ as_l i ttl address latch enable/address strobe: the exact function of this input pin depends upon which mode the microprocessor interface has been configured to operate in, as described below. intel-asynchronous mode - ale if the microprocessor interface (of the xrt94l33) has been configured to operate in the inte l-asynchronous mode, then this active-high input pin is used to latch the address (present at the microprocessor interface address bus input pins (a[14:0]) into the xrt94l33 microprocessor interface block and to indicate the start of a read or write cycle. pulling this input pin ?high? enables the input bus drivers for the address bus input pins (a[14:0]). the contents of the address bus will be latched into the xrt94l33 microprocessor interface circuitry, upon the falling edge of this input signal. motorola-asynchronous (68k) mode ? as* if the microprocessor interface has been configured to operate in the motorola-asynchronous mode, then this active-low input pin is used to latch the data (resid ing on the address bus, a[14:0]) into the microprocessor interface circuitry of the xrt94l33. pulling this input pin ?low? enables the input bus drivers for the address bus input pins. the contents of the address bus will be latched into the microprocessor interface circuitry, upon the rising edge of this signal. powerpc 403 mode ? no function ? tie to gnd : if the microprocessor interface has been configured to operate in the powerpc 403 mode, then this input pin has no role nor function and should be tied to gnd. ae19 pcs_l i ttl chip select input: the user must assert this active low signal in order to select the microprocessor interface for read and write operations between the microprocessor and the xrt94l33 on-chip registers, lapd and trace buffer locations.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 8 p in # s ignal n ame i/o s ignal t ype d escription ad18 prdy_l/ dtack* rdy o cmos ready or dtack output: the exact function of this input pin depends upon wich mode the microprocessor interface has been configured to operate in, as described below. intel asynchronous mode ? rdy* - ready output: if the microprocessor interface has been configured to operate in the intel-asyncrhronous mode, then this output pin will function as the ?active-low? ready output. during a read or write cycle, the microprocessor interface block will toggle this output pin to the logic ?low? level only when it (the microprocessor interface) is ready to complete or terminate the current read or write cycle. once the microprocessor has determined that this input pin has toggled to the logic ?low? level, then it is now safe for it to move on and execute the next read or write cycle. if (during a read or write cycle) the microprocessor interface block is holding this output pin at a logic ?high? level, then the microprocessor is expected to extend this read or write cycle, until it detect this output pin being toggled to the logic low level. motorola mode ? dtack* - data transfer acknowledge output: if the microprocessor interface has been configured to operate in the motorola-asynchronous mode, then this output pin will function as the ?active-low? dtack* ouytput. during a read or write cycle, the microprocessor interface block will toggle this output pin to the logic low level, only when it (the microprocessor interface) is ready to complete or terminate the current read or write cycle. once the microprocessor has determined that this input pin has toggled to the logic ?low? leve, then it is now safe for it to move on and execute the next read or write cycle. if (during a read or write cycle) the microprocessor interface block is holding this output pin at a logic ?high? level, then the microprocessor is expected to extend this read or write cycle, until it detects this output pin being toggled to the logic low level. powerpc 403 mode ? rdy ? ready output: if the microprocessor interface has been configured to operate in the powerpc 403 mode, then this output pin will function as the ?active-high? ready output. during a read or write cycle, the microprocessor interface block will toggle this output pin to the logic high level, only when it (the microprocessor interface) is ready to complete or terminate the current read or write cycle. once the microprocessor has sampled this signal being at a logic ?high? level (upon the rising edge of pclk) then it is now safe for it to move on and execute the next read or write cycle. the microprocessor interface will update the state of this output pin upon the rising edge of pclk.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 9 p in # s ignal n ame i/o s ignal t ype d escription af21 pdben_l i ttl bi-directional data bus enable input pin: this input pin permits the user to either enable or tri-state the bi- directional data bus pins (d[7:0]), as described below. setting this input pin ?low? enables the bi-directional data bus. setting this input ?high? tri-states the bi-directional data bus. af20 pblast_l i ttl last burst transfer indicator input pin: if the microprocessor interface is operating in the intel-i960 mode, then this input pin is used to indicate (to the microprocessor interface block) t hat the current dat a transfer is the last data transfer within the current burst operation. the microprocessor should assert this input pin (by toggling it ?low?) in order to denote that the current read or write operation (within a burst operation) is the last operation of this burst operation. note: the user should connect this input pin to gnd whenever the microprocessor interface has been configured to operate in the intel-async, motorola 68k and ibm powerpc 403 modes. ag22 pint_l o cmos interrupt request output: this open-drain, active-low out put signal will be asserted when the mapper/framer device is requesting interrupt service from the microprocessor. this output pin should typically be connected to the ?inte rrupt request? input of the microprocessor. ab24 reset_l i ttl reset input: when this ?active-low? signal is asserted, the xrt94l33 will be asynchronously reset. when this occurs, all outputs will be ?tri- stated? and all on-chip registers will be reset to their ?default? values. ae18 direct_add_sel i ttl address location select input pin: this input pin must be pulled ?high? in order to permit normal operation of the micropr ocessor interface. sonet/sdh s erial l ine i nterface p ins t3 rxldat_p i lvpecl receive sts-3/stm-1 data ? positive polarity pecl input: this input pin, along with rxldat_n functions as the recovered data input, from the optical transceiver or as the receive data input from the system back-plane note: for aps (automatic protection switching) purposes, this input pin, along with ?rxldat_n? functions as the ?primary? sts-3/stm-1 re ceive data input port.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 10 p in # s ignal n ame i/o s ignal t ype d escription t2 rxldat_n i lvpecl receive sts-3/stm-1 data ? ne gative polarity pecl input: this input pin, along with rxldat_p functions as the recovered data input, from the optical transceiver or as the receive data input from the system back-plane. note: for aps (automatic protection switching) purposes, this input pin, along with ?rxldat_p? functions as the ?primary receive sts-3/stm-1 data input port? u2 rxldat_r_p i lvpecl receive sts-3/stm-1 data ? po sitive polarity pecl input ? redundant port: this input pin, along with ?rxldat_r_n? functions as the recovered data input, from the optical transceiver or as the receive data input from the system back-plane. note: for aps (automatic protection switching) purposes, this input pin, along with ?rxldat_r_n? functions as the ?redundant receive sts-3/stm-1 data input port?. u1 rxldat_r_n i lvpecl receive sts-3/stm-1 data ? negative polarity pecl input ? redundant port: this input pin, along with ?rxldat_r_p? functions as the recovered data input, from the optical transceiver or as the receive data input from the system back-plane. note: for aps (automatic protection switching) purposes, this input pin, along with ?rxldat_r_n? functions as the ?redundant receive sts-3/stm-1 data input port?. ae27 rxclk_19mhz o cmos 19.44mhz recovered output clock: this pin outputs a 19.44mhz clock signal that has been derived from the incoming sts-3/stm-1 line signal (via the receive sts-3/stm-1 clock and data recovery pll). if the user wishes to operate t he sts-3/stm-1 interface in the ?loop-timing? mode, then the user should route this particular signal through a ?narrow-band? pll (in order to attenuate any jitter within this signal) prior to routing it to the refttl input pin. p3 refclk_p i lvpecl transmit reference clock ? positive polarity pecl input: this input pin, along with ?refclk_n? and ?refttl? can be configured to function as the timing source for the sts-3/stm-1 transmit interface block. if the user configures these two input pins to function as the timing source, then the user must apply a 155.52mhz clock signal, in the form of a pecl signal to these input pins. the user can configure these two inputs to function as the timing source by writing the appropriate data into the ?transmit line interface control register ? (address location = 0x0383) note: users should set this pin to ?1? if ?refttl? clock input is used
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 11 p in # s ignal n ame i/o s ignal t ype d escription p2 refclk_n i lvpecl transmit reference clock ? negative polarity pecl input: this input pin, along with ?refclk_p? and ?refttl? can be configured to function as the timing source for the sts-3/stm-1 transmit interface block. if the user configures these two input pins to function as the timing source, then the user must apply a 155.52mhz clock signal, in the form of a pecl signal to these input pins. the user can configure these two inputs to function as the timing source by writing the appropriate data into the ?transmit line interface control register ? (address location = 0x0383) note: users should set this pin to ?0? if ?refttl? clock input is used p5 txldato_p o lvpecl transmit sts-3/stm-1 data - positive polarity pecl output: this output pin, along with txldato_n functions as the transmit data output, to the op tical transceiver or to the system back-plane. for ?high-speed? back-plane applications, the user should note that data is output from these output pins upon the rising/falling edge of ?txlclko_p/txlclko_n?. note: for aps (automatic protection switching) purposes, this output pin, along with ?txldato_n? functions as the ?primary? transmit sts-3/ stm-1 data output port. p6 txldato_n o lvpecl transmit sts-3/stm-1 data ? negative polarity pecl output: this output pin, along with txldato_p functions as the transmit data output, to the op tical transceiver or to the system back-plane. for ?high-speed? back-plane applications, the user should note that data is output from these output pins upon the rising/falling edge of txlclko_p/txlclko_n. note: for aps (automatic protection switching) purposes, this output pin, along with ?txldato_p? functions as the ?primary? transmit sts-3/ stm-1 data output port. m4 txldato_r_p o lvpecl transmit sts-3/stm-1 data - po sitive polarity pecl output - redundant port: this output pin, along with txldato_r_n functions as the transmit data output, to the op tical transceiver or to the system back-plane. for ?high-speed? back-plane applications, the user should note that data is output from these output pins upon the rising/falling edge of ?txlclko_r_p/txlclko_r_n?). note: for aps (automatic protection switching) purposes, this output pin, along with ?txldato_n? functions as the ?redundant? transmit sts-3/stm-4 data output port.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 12 p in # s ignal n ame i/o s ignal t ype d escription m3 txldato_r_n o lvpecl transmit sts-3/stm-1 data - negative polarity pecl output - redundant port: this output pin, along with txldato_r_p functions as the transmit data output, to t he optical transceiver (for transmission to remote terminal equipment) or to the system back-plane (for transmission to some other system board) for ?high-speed? back-plane applications, the user should note that data is output from these output pins upon the rising/falling edge of ?txlclko_r_p/txlclko_r_n?). note: for aps (automatic protecti on switching) purposes, this output pin, along with ?txldato_r_p? functions as the ?redundant? transmit sts-3/stm-1 data output port. n6 txlclko_p o lvpecl transmit sts-3/stm-1 clock ? positive polarity pecl output: this output pin, along with txlclko_n functions as the transmit clock output signal. these output pins are typically used in ?high-speed? back-plane applications. in this case, outbound sts-3/stm-1 data is output via the ?txldato_p/txldato_n? output pins upon the rising edge of this clock signal. note: for aps (automatic protection switching) purposes, this output pin, along with ?txlclko_n? functions as the ?primary transmit output clock? signal. n5 txlclko_n o lvpecl transmit sts-3/stm-1 clock ? negative polarity pecl output: this output pin, along with txlclko_p functions as the transmit clock output signal. these output pins are typically used in ?high-speed? back-plane applications. in this case, outbound sts-3/stm-1 data is output via the ?txldato_p/txldato_n? output pins upon the falling edge of this clock signal. note: for aps (automatic protection switching) purposes, this output pin, along with ?txlclko_n? functions as the ?primary transmit output clock? signal. m1 txlclko_r_p o lvpecl transmit sts-3/stm-1 clock ? positive polarity pecl output ? redundant port: this output pin, along with txlclko_r_n functions as the transmit clock output signal. these output pins are typically used in ?high-speed? back-plane applications. in this case, outbound sts-3/stm-1 data is output via the ?txldato_r_p/txldato_r_n? output pins upon the rising edge of this clock signal. note: for aps (automatic protection switching) purposes, this output pin, along with ?txlclko_r_n? functions as the ?redundant transmit output clock? signal.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 13 p in # s ignal n ame i/o s ignal t ype d escription m2 txlclko_r_n o lvpecl transmit sts-3/stm-1 clock ? negative polarity pecl output ? redundant port: this output pin, along with txlclko_r_p functions as the transmit clock output signal. these output pins are typically used in ?high-speed? back-plane applications. in this case, outbound sts-3/stm-1 data is output via the ?txldato_r_p/txldato_r_n? output pins upon the rising edge of this clock signal. note: for aps (automatic protection switching) purposes, this output pin, along with ?txlclko_r_p? functions as the ?redundant transmit output clock? signal. p1 refttl i ttl 19.44mhz or 77.76mhz clock sy nthesizer reference clock input pin: the exact function of this input pin depends upon whether the user enables the ?clock synthesizer? block or not. if clock synthesizer is enabled. if the ?clock synthesizer? block is enabled, then it will be used to generate the 155.52mhz, 19. 44mhz and/or 77.76mhz clock signal for the sts-3/stm-1 block. in this mode, the user should apply a clock signal of either of the following frequencies to this input pin. ? 19.44 mhz ? 38.88 mhz ? 51.84 mhz ? 77.76 mhz afterwards, the user needs to write the appropriate data into the ?transmit line interface control register? (address location = 0x0383) in order to (1) configure the clock synthesizer block to accept any of the above-ment ioned signals and generate a 155.52mhz, 19.44mhz or 77.76mhz clock signal, (2) to configure the clock synthesizer to function as the clock source for the sts-3/stm-1 block. if clock synthesizer is not enabled: if the ?clock synthesizer? block is not enabled, then it will not be used to generate the 19. 44mhz and/or 77.76mhz clock signal, for the sts-3/stm-1 block. in this configuration seting, the user must apply a 19.44mhz clock signal to this input pin.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 14 p in # s ignal n ame i/o s ignal t ype d escription ag3 losttl i ttl loss of optical carrier input ? primary: the user is expected to connect the ?loss of carrier? output (from the optical transceiver) to this input pin. if this input pin and the lospecl_p pin are pulled ?high?, or if both of these input pins are pu lled ?low?, tthen the receive sts- 3 toh processor block will declare a ?loss of optical carrier? condition. note: this input pin is only active if the ?primary port? is active. this input pin is inactive if the ?redundant port? is active. ag25 losttl_r i ttl loss of optical carrier input ? redundant: the user is expected to connect the ?loss of carrier? output (from the optical transceiver) to this input pin. if this input pin and the lospecl_r are pulled ?high?, or if both of these input pins are pulled ?l ow?, then the receive sts-3 toh processor block will declare a ?loss of optical carrier? condition. note: this input pin is only active if the ?redundant port? is active. this input pin is inactive if the ?primary port? is active. l4 lospecl_p i lvpecl loss of pecl interface input ? primary: if this input pin is pulled ?high?, then the receive sts-3 toh processor block will declare a ?loss of pecl interface? condition. note: this input pin is only active if the ?primary port? is active. this input pin is inactive if the ?redundant port? is active. l3 lospecl_r i lvpecl loss of pecl interface input ? redundant: if this input pin is pulled ?high?, then the receive sts-3 toh processor block will declare a ?loss of pecl interface? condition. note: this input pin is only active if the ?redundant port? is active. this input pin is inactive if the ?primary port? is active. v1 lockdet o cmos lock detect output pin ? clock and data recovery pll block this output pin indicates whether the clock and data recovery pll block has obtained lock to incoming sts-3/stm-1 signal or not. this pin pulses high if internal vco frequency is within 0.05% of external reference clock this pin pulses low if internal vco frequency is beyond 0.05% of external reference clock, and loss of lock is declared.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 15 sts-3/stm-1 t elecom b us i nterface ? t ransmit d irection e1 txa_clk/ txapsclk o i/o cmos transmit sts-3/stm-1 telecom bus interface - clock output signal: this output clock signal functions as the clock source for the transmit sts-3/stm-1 telecom bus. all signals, that are output via the transmit sts-3/stm-1 te lecom bus interface (e.g., txa_c1j1, txa_alarm, txa_dp , txa_pl and txa_d[7:0]) are updated upon the rising edge of this clock signal. this clock signal operates at 19. 44mhz and is derived from the clock synthesizer block. transmit payload aps bus interface clock input/output signal ? txapsclk: this pin can only be configured to operate in this mode if the xrt94l33 has been configured to operate in either the ?atm uni? over ?ppp over sts-3c? mode. f2 txa_c1j1 o cmos transmit sts-3/stm-1 telecom bus interface - c1/j1 byte phase indicator output signal: this output pin pulses ?high? under the following two conditions. ? whenever the c1 byte is being output via the ?txa_d[7:0]? output, and ? whenever the j1 byte is being output via the ?txa_d[7:0]? output. notes: 1. the transmit sts-3/stm-1 te lecom bus interface will indicate that it is currently transmitting the c1 byte (via the txa_d[7:0] output pins), by pulsing this output pin ?high? (for one period of ?txa_clktxa_ck?) and keeping the ?txa_pl? output pin pulled ?low?. 2. the transmit sts-3/stm-1 teleco m bus will indicate that it is currently transmitting the j1 byte (via the txa_d[7:0] output pins), by pulsing this output pin ?high? (for one period of ?txa_clktxa_ck?) while the ?txa_pl? output pin is pulled ?high?. 3. this output pin is only active if the transmit sts-3/stm-1 telecom bus interface block is enabled and is configured to operate in the ?re-phase off? mode.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 16 e2 txa_alarm/ txapspar o i/o cmos ttl/ cmos transmit sts-3/stm-1 telecom bus interface ? alarm indicator output signal: this output pin pulses ?high?, co incident to the instant that the transmit sts-3/stm-1 telecom bus interface outputs an byte of any sts-1 or sts-3c signal (via the ?txd_d[7:0]? output pins) that is carrying an ais-p indicator. this output pin is ?low? for all other conditions. note: this output pin is only active if the transmit sts-3/stm- 1 telecom bus interface is enabled and has been configured to operate in the ?re-phase off? mode. transmit payload aps bus in terface ? parity input/output pin: this pin can only be configured to operate in this role/function if the xrt94l33 has been configured to operate in the ?atm uni? or the ?ppp over sts-3c? mode. please see the ?xrt94l33_pin_description_atm_ppp.pdf? document for more information. h3 txa_dp o cmos transmit sts-3/stm-1 telecom bus interface ? parity output pin: this output pin can be configured to function as either one of the following. the even or odd parity value of the bits which are output via the ?txa_d[7:0]? output pins. the even or odd parity value of the bits which are being output via the ?txa_d[7:0]? output pins and the states of the ?txa_pl? and ?txa_c1j1? output pins. notes: a. the user can make any one of these configuration selections by writing the appropriate value into the ?telecom bus control? register (address location = 0x0137). b. this output pin is only active if the xrt94l33 has been configured to output its sts-3/stm- 1 or sts-3c data via the transmit sts-3/stm- 1 telecom bus interface block.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 17 g4 txsbfp i ttl transmit sts-3/stm-1 frame alignment sync input: the transmit sts-3 toh processor block can be configured to initiate its generation of a ne w ?outbound? sts-3/stm-1 frame based upon an externally supplied 8khz clock signal to this input pin. if the user opts to use this feature, then the transmit sts- 3/stm-1 telecom bus interface will begin transmitting the very first byte of given sts-3 or stm-1 frame, upon sensing a rising edge (of the 8khz signal) at this input pin. notes: 1. if the user connects this input pin to gnd, then the transmit sts-3 toh processor block will generate its ?outbound? sts-3/stm-1 frames asynchronously, with respect to any input signal. 2. this input signal must be synchronized with the signal that is supplied to the refttl input pin. failure to insure this will result in bit errors being generated within the outbound sts- 3/stm-1 signal. 3. the user must supply an 8khz pulse (to this input pin) that has a width of approximatel y 51.4412.8ns (one 19.44mhz clock period). the user must not apply a 50% duty cycle 8khz signal to this input pin. 4. register ?hrsync_dly? (address location: 0x0135) defines the timing for txsbfp input pin. k5 txa_pl/ txapsreq o i/o cmos ttl/ cmos transmit sts-3/stm-1 telecom bus interface ? payload data indicator output signal: this output pin indicates whether the transmit sts-3/stm-1 telecom bus interface is currently placing a transport overhead byte or a ?non-transport overhead byte (e.g., sts-1 spe, sts- 3c spe, vc-3 or vc-4 data) via the ?txa_d[7:0]? output pins. this output pin is pulled ?low? fo r the duration that the transmit sts-3/stm-1 telecom bus interface is transmitting a transport overhead byte via the ?txa_d[7:0]? output pins. conversely, this output pin is pulled ?high? for the duration that the sts-3/stm-1 transmit telecom bus is transmitting something other than a transport overhead byte via the ?txa_d[7:0]? output pins. transmit payload aps bus interface ? request input/output pin: this pin can only be configured to operate in this role if the xrt94l33 has been configured to operate in either the ?atm uni? or ?ppp over sts-3c? mode.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 18 j4 g3 d1 f3 j5 h4 d2 e3 txa_d0/ txapsdat0 txa_d1/ txapsdat1 txa_d2/ txapsdat2 txa_d3/ txapsdat3 txa_d4/ txapsdat4 txa_d5/ txapsdat5 txa_d6/ txapsdat6 txa_d7/ txapsdat7 o o i/o cmos cmos cmos/ ttl transmit sts-3/stm-1 telecom bus interface ? transmit output data bus pins: these 8 output pins function as the ?transmit sts-3/stm-1 telecom bus interface? ? data bus output pins. if the sts- 3/stm-1 telecom bus interface is enabled, then all ?outbound? sts-3/stm-1 data is output via these pins (in a byte-wide manner), upon the rising edge of the ?txa_clk? output clock signal. transmit payload aps bus interface ? data input/output pins: these pins can only be configured to operate in this function/role if the xrt94l33 has been config ured to operate in the ?atm uni? or ?ppp over sts-3c? mode. sts-3/stm-1 t elecom b us i nterface ? r eceive d irection w2 rxd_clk/ rxapsclk i i i/o ttl ttl ttl/ cmos receive sts-3/stm-1 telecom bus interface - clock input signal: this input clock signal functions as the clock source for the receive sts-3/stm-1 telecom bus interface block. all input signals are sampled upon the falling edge of this input clock signal. this clock signal should operate at 19.44mhz. note: this input pin is only used if the ?sts-3/stm-1 telecom bus? has been enabled. it should be connected to gnd otherwise. receive payload aps bus interface - clock input/output signal: this input can only be configured to operate in this role/function if the xrt94l33 has been config ured to operate in either the ?atm uni? or ?ppp over sts-3c? mode.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 19 aa3 rxd_pl i ttl receive sts-3/stm-1 telecom bus interface ? payload data indicator output signal: this input pin indicates whether or not the receive sts-3/stm-1 telecom bus interface is currently receiving transport overhead bytes or ?non-transport overhead bytes (e.g., sts-1 spe, sts- 3c spe,vc-3 or vc-4 data) via the ?rxd_d[7:0]? input pins. this input pin should be pulled ?low? for the duration that ?sts- 3/stm-1 receive sts-3/stm-1 telecom bus interface is receiving a transport overhead byte via the ?rxd_d[7:0]? input pins. conversely, this input pin should be pulled ?high? for the duration that the receive sts-3/stm-1 telecom interface bus is receiving something other than a transport overhead byte via the ?rxd_d[7:0]? input pins. note: the user should connect this pin to gnd if the sts- 3/stm-1 telecom bus is not enabled. ad1 rxd_c1j1/ rxapsval i i/o ttl ttl/ cmos receive sts-3/stm-1 telecom bus interface - c1/j1 byte phase indicator input signal/r eceive aps valid indicator input/output signal: the exact function of this input pin depends upon (1) whether the sts-3/stm-1 telecom bus interface has been enabled or not, and (2) whether the payload aps bus has been enabled or not. if the sts-3/stm-1 telecom bus interface has been enabled ? rxd_c1j1: this input pin should be pulsed ?high? during both of the following conditions. a. coincident to whenever the c1/j0 byte is being applied to the receive sts-3/stm-1 telecom bus ? data input pins (rxd_d[7:0]). b. b. coincident to whenever the j1 byte is being applied to the receive sts-3/stm-1 telecom bus ? data input pins (rxd_d[7:0]) input. note: this input pin should be pulled ?low? during all other times. receive payload aps bus interface ? data valid input/output signal: this pin can only be configured to operate in this role if the xrt94l33 has been configured to operate in either the ?atm uni? or ?ppp over sts-3c? mode.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 20 ab3 rxd_dp i ttl receive sts-3/stm-1 telecom bus interface ? parity input pin: this input pin can be configured to function as one of the following. the even or odd parity value of t he bits which are input via the ?rxd_d[7:0]? input pins. the even or odd parity value of the bits which are being input via the ?rxd_d[7:0]? input and t he states of the ?rxd_pl? and ?rxd_c1j1? input pins. notes: 1. the user can make any on e of these configuration selections by writing the appropr iate value into the ?telecom bus control? register (address location = 0x0137). 2. the user should connect this pin to gnd if the sts-3/stm- 1 telecom bus interface is disabled. w1 rxd_alarm/ rxapspar i i/o ttl ttl/ cmos receive sts-3/stm-1 telecom bus interface ? alarm indicator input: this input pin pulses ?high? coincident to whether the receive sts-3/stm-1 telecom bus interface block is receiving a byte (via the ?rxd_d[7:0] input pins) t hat is a part of any sts-1 or sts-3c signal that is carrying the ais-p indicator. note: if the rxd_alarm input signal pulses ?high? for any given sts-1 signal (within the ?incoming? sts-3), then the corresponding receive sonet poh processor block will automatically declare the ais-p defect condition. rxapsparity ? receive payload aps bus interface ? parity input/output pin: this pin can only be configured to operate in this role if the xrt94l33 has been configured to operate in either the ?atm uni? or ?ppp over sts-3c? mode.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 21 y2 ad2 ac3 aa4 ab4 y1 ad3 aa5 rxd_d0/ rxhrdat0/ rxapsdat0 rxd_d1 rxhrdat1/ rxapsdat1 rxd_d2 rxhrdat2/ rxapsdat2 rxd_d3 rxhrdat3/ rxapsdat3 rxd_d4 rxhrdat4/ rxapsdat4 rxd_d5 rxhrdat5/ rxapsdat5 rxd_d6 rxhrdat6/ rxapsdat6 rxd_d7 rxhrdat7/ rxapsdat7 i i i/o ttl ttl ttl/ cmos receive sts-3/stm-1 telecom bus interface ? receive input data bus pins - rxd_d[7:0]: these 8 input pins function as the receive sts-3/stm-1 telecom bus interface - input data bus. all incoming sts- 3/stm-1 data is sampled and la tched (into the xrt94l33, via these input pins) upon the falling edge of the ?rxd_clk? input clock signal. rxhrdat[7:0]: receive data inputs for high-rate device receive payload aps bus interface ? data bus input/output pins: these pins can only be configured to function in this role if the xrt94l33 has been configured to operate in the ?atm uni? or ?ppp over sts-3c? mode. thes e pins cannot be configured to support ?payload aps? operation if the xrt94l33 has been configured to operate in an ?aggregation? role.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 22 sonet/sdh o verhead i nterface ? t ransmit d irection h6 txtohclk o cmos transmit toh input port ? clock output: this output pin, along with the ?txtohenable?, ?txtohframe? output pins and the ?txtoh? and ?txtohins? input pins function as the ?transmit toh input port?. the transmit toh input port permits the user to externally insert his/her own value(s) for the toh bytes (within the outbound sts-3/stm-1 signal). this output pin provides the user with a clock signal. if the ?txtohenable? output pin is ?high? and if the ?txtohins? input pin is pulled ?high?, then the user is expected to provide a given bit (within the ?toh?) to the ?txtoh? input pin, upon the falling edge of this clock signal. the data, residing on the ?txtoh? input pin will be latched into the xrt94l33 upon the rising edge of this clock signal. note: the transmit toh input port only supports the insertion of the toh within the very first sts-1 of the outbound sts-3 signal. g5 txtohenable o cmos transmit toh input port ? toh enable (or ready) indicator: this output pin, along with the ?txtohclk?, ?txtohframe? output pins and the ?txtoh? and ?txtohins? input pins function as the ?transmit toh input port?. this output pin will toggle and remain ?high? anytime the ?transmit toh input port? is r eady to externally accept toh data via the ?txoh? input pin. to externally insert user values of toh into the ?outbound? sts-3 data stream via the ?tr ansmit toh input port?, do the following. ? continuously sample the st ate of ?txtohframe? and this output pin upon the risi ng edge of ?txtohclk?. ? whenever this output pin pulses ?high?, then the user?s external circuitry should drive the ?txtohins? input pin ?high?. ? next, the user should output the next toh bit, onto the ?txtoh? input pin, upon the rising edge of ?txtohclk?
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 23 f8 txtoh i ttl transmit toh input port ? input pin: this input pin, along with the ?txtohins? input pin, the ?txtohenable? and ?txtohframe? and ?txtohclk? output pins function as the ?tr ansmit toh input port?. to externally insert user va lues of toh into the outbound sts-3 data stream via the ?tr ansmit toh input port?, do the following. ? continuously sample the state of ?txtohframe? and ?txtohenable? upon the rising edge of ?txtohclk. ? whenever ?txtohenable? pulses ?high?, then the user?s external circuitry should drive the ?txtohins? input pin ?high?. ? next, the user should output the next toh bit, onto this input pin, upon the rising edge of ?txtohclk?. the ?transmit toh input port? will sample the data (on this input pin) upon the falling edge of ?txtohclk?. note: data at this input pin will be ignored (e.g., not sampled) unless the ?txtohenable? output pin is ?high? and the ?txtohins? input pin is pulled ?high?. e8 txtohframe o cmos transmit toh input port ? sts-3/stm-1 frame indicator: this output pin, along with ?t xtohclk?, ?txtoh enable output pins, and the ?txtoh? and ?txtohins? input pins function as the ?transmit toh input port?. this output pin will pulse high (for one period of txtohclk), one ?txtohclk? clock period prior to the first ?toh bit? of a given sts-3 frame, being expect ed via the ?txtoh? input pin. to externally insert user values of toh into the ?outbound? sts-3 data stream via the ?tr ansmit toh input port?, do the following. ? continuously sample the state of ?txtohenable? and this output pin upon the risi ng edge of ?txtohclk?. ? whenever the ?txtohenable? output pin pulse ?high?, then the user?s external circuitry should drive the ?txtohins? input pin ?high?. ? next, the user should output the next toh bit, onto the ?txtoh? input pin, upon the rising edge of ?txtohclk?. note: the external circuitry (which is being interfaced to the ?transmit toh input port ? can use this particular output pin to denote the boundary of sts-3 frames.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 24 d6 txtohins i ttl transmit toh input port ? insert enable input pin: this input pin, along with the ?txtoh? input pin, and the ?txtohenable?, ?txtohframe? and ?txtohclk? output pins function as the ?transmit toh input port?. this input pin permits the user to either enable or disable the ?transmit toh input port?. if this input pin is ?low?, t hen the ?transmit toh input port? will be disabled and will not sample and insert (into the ?outbound? sts-3 data stre am) any data residing on the ?txtoh? input, upon the rising edge of ?txtohclk? if this input pin is ?high?, t hen the ?transmit toh input port? will be enabled. in this mode, whenever the ?txtohenable? output pin is also ?high?, the ?transmit toh input port? will sample and latch any data that is presented on the ?txtoh? input pin, upon the rising edge of ?txtohclk?. to externally insert user values of toh into the ?outbound? sts-3 data stream via the ?tr ansmit toh input port?, do the following. ? continuously sample the state of ?txtohframe? and ?txtohenable? upon the rising edge of ?txtohclk?. ? whenever the ?txtohenable? output pin is sampled ?high? then the user?s external circuitry should drive this input pin ?high?. ? next, the user should output the next toh bit, onto the ?txtoh? input pin, upon the falli ng edge of ?txtohclk?. the ?transmit toh input port? will sample the data (on this input pin) upon the falling edge of ?txtohclk?.] notes: 1. data applied to the ?txtoh? input pin will be sampled according to the following insertion priority scheme: 2. for dcc, e1, f1, e2 bytes, ?txtoh? input pin will be sampled if both ?txtohenable? and ?txtohins? are high. 3. for other toh bytes, ?txt oh? input pin will be sampled if both ?txtohenable? and ?txtohins? are high or if both ?txtohins? and ?software insertion enabled? are ?low?.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 25 b4 txldccenable o cmos transmit ? line dcc input po rt ? enable output pin: this output pin, along with the ?txtohclk? output pin and the ?txldcc? input pin permit the user to insert their value for the d4, d5, d6, d7, d8, d9, d10, d11 and d12 bytes into the transmit sts-3 toh processor block. the transmit sts-3 toh processor block will accept this data and will insert into the d4, d5, d6, d7, d8, d9, d 10, d11 and d12 byte-fields, within the ?outbound? sts-3 data-stream. the line dcc hdlc controller circuitry (which is connected to the ?txtohclk?, the ?txsd cc? and this output pin, is suppose to do the following. it should continuously monitor t he state of this output pin. whenever this output pin puls es ?high?, then the line dcc hdlc controller circuitry should place the next line dcc bit (to be inserted into the ?transmit sts-3 toh processor? block) onto the ?txldcc? input pin, upon the rising edge of ?txtohclk?. any data that is placed on the ?txldcc? input pin, will be sampled upon the falling edge of ?txohclk?. d7 txsdccenable o cmos transmit ? section dcc input port ? enable output pin: this output pin, along with the ?txtohclk? output pin and the ?txsdcc? input pin permit the user to insert their value for the d1, d2 and d3 bytes, into the transmit sts-3 toh processor block. the transmit sts-3 toh processor block will accept this data and will insert into the d1, d2 and d3 byte-fields, within the ?outbound? sts-3 data-stream. the section dcc hdlc controller circuitry (which is connected to the ?t xtohclk?, the ?txsdcc? and this output pin, is suppose to do the following. it should continuously monitor t he state of this output pin. whenever this output pin puls es ?high?, then the section dcc hdlc controller circuitry should place the next section dcc bit (to be inserted into the ?transmit sts-3 toh processor? block) onto the ?txsd cc? input pin, upon the rising edge of ?txtohclk?. any data that is placed on the ?txsdcc? input pin, will be sampled upon the falling edge of ?txohclk?.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 26 c5 txsdcc i ttl transmit - section dcc input port ? input pin: this input pin, along with the ?txsdccenable? and the ?txtohclk? output pins permit the user to insert their value for the d1, d2 and d3 bytes, into the transmit sts-3 toh processor block. the transmit sts-3 toh processor block will accept this data and insert it into the d1, d2 and d3 byte fields, within the ?outbound? sts-3 data-stream. the section dcc hdlc circuitry that is interfaced to this input pin, the ?txsdccenable? and t he ?txtohclk? pins is suppose to do the following. it should continuously m onitor the state of the ?txsdccenable? input pin. whenever the ?txsdccenable? input pin pulses ?high?, then the section dcc hdlc controller circuitry should place the next section dcc bit (to be inserted into the ?transmit sts-3 toh processor? block) onto this input pin upon the rising edge of ?txtohclk?. any data that is placed on the ?txsdcc? input pin, will be sampled upon the falling edge of ?txtohclk?. note: this pin should be connected to gnd if it is not used. d8 txldcc i ttl transmit - line dcc input port: this input pin, along with the ?txldccenable? and the ?txtohclk? pins permit the user to insert their value for the d4, d5, d6, d7, d8, d9, d10, d11 and d12 bytes, into the transmit sts-3 toh processor block. the transmit sts-3 toh processor block will accept this data and insert it into the d4, d5, d6, d7, d8, d9, d10, d11 and d12 byte-fields, within the ?outbound? st s-3 data-stream. whatever line dcc hdlc controller circuitry is interface to the this input pin, the ?txldc cenable? and the ?txtohclk? is suppose to do the following. it should continuously m onitor the state of the ?txldccenable? input pin. whenever the ?txldccenable? input pin pulses ?high?, then the section dcc interface circuitr y should place the next line dcc bit (to be inserted into the ?transmit sts-3 toh processor? block) onto the ?txldcc? input pin, upon the rising edge of ?txtohclk?. any data that is placed on the ?txldcc? input pin, will be sampled upon the falling edge of ?txtohclk?. note: this pin should be connected to gnd if it is not used.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 27 e9 txe1f1e2enable o cmos transmit e1-f1-e2 byte input port ? enable (or ready) indicator output pin: this output pin, along with the ?txtohclk? output pin and the ?txe1f1e2? input pin permit the user to insert their value for the e1, f1 and e2 bytes, into the transmit sts-3 toh processor block. the transmit sts-3 toh processor block will accept this data and will insert into the e1, f1 and e2 byte- fields, within the ?outbound? sts-3 data-stream. whatever external circuitry (which is connected to the ?txtohclk?, the ?txe1f1e2? and this output pin), is suppose to do the following. it should continuously monitor t he state of this output pin. whenever this output pin pulses ?high?, then the external circuitry should place the next ?orderwire? bit (to be inserted into the ?transmit sts-3 toh processor? block) onto the ?txe1f1e2? input pin, upon t he rising edge of ?txtohclk?. any data that is placed on the ?txe1f1e2? input pin, will be sampled upon the falling edge of ?txohclk?. c6 txe1f1e2frame o cmos transmit e1-f1-e2 byte input port ? framing output pin. this output pin pulses ?high? for one period of ?txtohclk?, one ?txtohclk? bit-period prior to the ?transmit e1-f1-e2 byte input port? expecting the very first byte of the e1 byte, within a given ?outbound? sts-3 frame. a4 txe1f1e2 i ttl transmit e1-f1-e2 byte input port ? input pin: this input pin, along with the ?txe1f1e2enable? and the ?txtohclk? output pins permit the user to insert their value for the e1, f1 and e2 bytes, into the transmit sts-3 toh processor block. the transmit sts-3 toh processor block will accept this data and insert it into the e1, f1 and e2 byte fields, within the ?outbound? sts-3 data-stream. whatever external circuitry that is interfaced to this input pin, the ?txe1f1e2enable? and the ?t xtohclk? pins is suppose to do the following. it should continuously m onitor the state of the ?txe1f1e2enable? input pin. whenever the ?txe1f1e2enable? input pin pulses ?high?, then the external circuitry should place the next ?orderwire? bit (to be inserted into the ?transmit sts-3 toh processor? block) onto this input pin upon the rising edge of ?txtohclk?. any data that is placed on the ?txe1f1e2? input pin, will be sampled upon the falling edge of ?txtohclk?. note: this pin should be connected to gnd if it is not used.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 28 c7 txpoh i ttl transmit path overhead input port ? input pin. this pin is used for the transmit au-4/vc-4 mapper poh processor block when tug-3 mapping is used. this input pin permits the user to insert the poh data into the transmit au-4/vc-4 mapper poh processor blocks for insertion and transmission via the ?outbound? sts-3 signal. in this mode, the external circuitry (which is being interfaced to the ?transmit path overhead input port? is suppose to monitor the following output pins; ? txpohframe_n ? txpohenable_n ? txpohclk_n the ?txpohframe_n? output pin will toggle ?high? upon the rising edge of ?txpohclk _n? approximately one ?txpohclk_n? period prior to the ?txpoh? port being ready to accept and process the first bit within j1 byte (e.g., the first poh byte). the ?txpohframe_n? output pin will remain ?high? for eight consecutive ?txpohclk_n? periods. the external circuitry should use this pin to note sts-1 spe frame boundaries. the ?txpohenable_n? output pin will toggle ?high? upon the rising edge of ?txpohclk _n? approximately one ?txpohclk_n? period prior to the ?txpoh? port being ready to accept and process the first bit within a given poh byte. to externally insert a given poh byte: (1) assert the ?txpohins_n? input pin by toggling it ?high?, and (2) place the value of the first bit (within this particular poh byte) on this input pin upon the very next rising edge of ?txpohclk_n?. this data bit will be sampled upon the very next falling edge of ?txpohclk_n?. the external circuitry should continue to keep the ?txpohins_n? input pin ?high? and advancing the next bits (within the poh bytes) upon each rising edge of ?txpohclk_n?. d9 txpohclk o ttl transmit path overhead input port ? clock output pin: this pin is used for the transmit au-4/vc-4 mapper poh processor block when tug-3 mapping is used. this output pin, along with ?txpoh?, ?txpohenable?, ?txpohins? and ?txpohframe? function as the ?transmit path overhead (txpoh) input port?. the ?txpohframe? and ?txpohenable? output pins are updated upon the falling edge this clock output signal. the ?txpohins? input pins and the data residing on the ?txpoh? input pins are sampled upon the next falling edge of this clock signal.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 29 b5 txpohframe o ttl transmit path overhead input port ? frame output pin: this pin is used for the transmit au-4/vc-4 mapper poh processor block when tug-3 mapping is used. this output pin, along with t he ?txpoh?, ?txpohenable?, ?txpohins? and ?txpohclk? function as the ?transmit path overhead input port?. if the user is only inserting poh data via these input pins: note: in this mode, the ?txpoh? port will pulse these output pins ?high? whenever it is ready to accept and process the j1 byte (e.g., the very first poh byte) via this port. c8 txpohins i ttl transmit path overhead input port ? insert enable input pin: this pin is used for the transmit au-4/vc-4 mapper poh processor block when tug-3 mapping is used. these input pins, along with ?txpoh?, ?txpohenable?, ?txpohframe? and ?txpohclk? function as the ?transmit path overhead (txpoh) input port. these input pins permit the user to enable or disable the ?txpoh? input port. if these input pins are pulled ?h igh?, then the ?txpoh? port will sample and latch data via the corresponding ?txpoh? input pins, upon the falling edge of ?txpohclk?. note: conversely, if these input pins are pulled ?low?, then the ?txpoh? port will not sample and latch data via the corresponding ?txpoh? input pins. b6 txpohenable o ttl transmit path overhead input port ? poh indicator output pin: this pin is used for the transmit au-4/vc-4 mapper poh processor block when tug-3 mapping is used. these output pins, along with ?txpoh?, ?txpohins?, ?txpohframe? and ?txpohclk? function as the ?transmit path overhead (txpoh) input port?. these output pins will pulse ?high? anytime the ?txpoh? port is ready to accept and process poh bytes. these output pins will be ?low? at all other times.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 30 e10 b8 d11 txpoh_0 txpoh_1 txpoh_2 i ttl transmit path overhead input port ? input pin. these input pins permit the user to insert the poh data into each of the 3 transmit sonet poh processor blocks (for insertion and transmission via the ?outbound? sts-3 signal. if the user is only inserting poh data via these input pins: in this mode, the external circuitry (which is being interfaced to the ?transmit path overhead input port? is suppose to monitor the following output pins; ? txpohframe_n ? txpohenable_n ? txpohclk_n the ?txpohframe_n? output pin will toggle ?high? upon the rising edge of ?txpohclk _n? approximately one ?txpohclk_n? period prior to the ?txpoh? port being ready to accept and process the first bit within j1 byte (e.g., the first poh byte). the ?txpohframe_n? output pin will remain ?high? for eight consecutive ?txpohclk_n? periods. the external circuitry should use this pin to note sts-1 spe frame boundaries. the ?txpohenable_n? output pin will toggle ?high? upon the rising edge of ?txpohclk _n? approximately one ?txpohclk_n? period prior to the ?txpoh? port being ready to accept and process the first bit within a given poh byte. to externally insert a given poh byte: (1) assert the ?txpohins_n? input pin by toggling it ?high?, and (2) place the value of the first bit (within this particular poh byte) on this input pin upon the very next rising edge of ?txpohclk_n?. this data bit will be sampled upon the very next falling edge of ?txpohclk_n?. the external circuitry should continue to keep the ?txpohins_n? input pin ?high? and advancing the next bits (within the poh bytes) upon each rising edge of ?txpohclk_n?. a5 a6 a7 txpohclk_0 txpohclk_1 txpohclk_2 o cmos transmit path overhead input port ? clock output pin: these output pins, along with ?txpoh_n?, ?txpohenable_n?, ?txpohins_n? and ?txpohframe? function as the ?transmit path overhead (txpoh) input port?. the ?txpohframe? and ?txpohenable? output pins are updated upon the falling edge this clock output signal. the ?txpohins_n? input pins and the data residing on the ?txpoh_n? input pins are sampled upon the next falling edge of this clock signal.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 31 c9 c10 a8 txpohframe_0 txpohframe_1 txpohframe_2 o cmos transmit path overhead input port ? frame output pin: these output pins, along with the ?txpoh_n?, ?txpohenable_n?, ?txpohins_n? and ?txpohclk_n? function as the ?transmit path overhead input port?. the exact function of these out put pins depends upon whether the user inserting poh or to h data via the ?txpoh_n? input pins. if the user is only inserting poh data via these input pins: the ?txpoh? port will pulse these output pins ?high? whenever it is ready to accept and process the j1 byte (e.g., the very first poh byte) via this port. notes: 1. the externally circuitry can determine whether the ?txpoh? port is expecting the a1 byte or the j1 byte, by checking the state of the corresponding ?txpohenable? output pin. if the ?txpohe nable_n? output pin is ?low? while the ?txpohframe_n? output pin is ?high?, then the ?txpoh? port is ready to process the a1 (toh) bytes. 2. if the ?txpohenable_n? output pin is ?high? while the ?txpohframe_n? output pin is ?high?, then the ?txpoh? port is ready to process the j1 (poh) bytes. d10 e11 c11 txpohins_0 txpohins_1 txpohins_2 i ttl transmit path overhead input port ? insert enable input pin: these input pins, along with ?txpoh_n?, ?txpohenable_n?, ?txpohframe_n? and ?txpohclk_n ? function as the transmit path overhead (txpoh) input port. these input pins permit the user to enable or disable the ?txpoh? input port. if these input pins are pulled ?h igh?, then the ?txpoh? port will sample and latch data via the corresponding ?txpoh? input pins, upon the falling edge of ?txpohclk_n?. conversely, if these input pins are pulled ?low?, then the ?txpoh? port will not sample and latch data via the corresponding ?txpoh? input pins. note: if the ?txpohins_n? input pin is pulled ?low?, this setting will be overridden if the user has configured the ?transmit sonet/sts-1 poh processor? or ?transmit sts-1 toh processor? blocks to accept certain poh or toh overhead bytes via the external port. b7 b9 b10 txpohenable_0 txpohenable_1 txpohenable_2 o cmos transmit path overhead input port ? poh indicator output pin: these output pins, along with ?txpoh_n?, ?txpohins_n?, ?txpohframe_n? and ?txpohclk_n? function as the ?transmit path overhead (txpoh) input port?. these output pins will pulse ?high? anytime the ?txpoh? port is ready to accept and process poh bytes. these output pins will be ?low? at all other times. t ransmit l ine / s ystem s ide i nterface p ins
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 32 c12 txds3clk_0 txe3clk_0 i ttl transmit ds3/e3 reference clock input ? channel 0 (not used for mapper applications): the exact manner in which the user should handle this input pin depends upon whether channel 0 has been configured to operate in the mapper mode or in the atm uni/ppp mode. if channel 0 is configured to operate in the mapper mode : if channel 0 has been configured to operate in the mapper mode, then this input pin supports no function, and should, therefore, be connected to gnd. if channel 0 is configured to operate in the atm uni/ppp/clear channel mode: if channel 0 (within the xrt94l33) has been configured to operate in the atm uni/ppp mode, then this input pin will function as the timing reference clock signal for the transmit sts-1/ds3/e3 framer block circ uitry, provided that channel 0 has been configured to operate in the local timing mode. if channel 0 has been configured to operate in the ds3 mode, then the user is expected to apply a 44.736mhz clock signal to this input pin. likewise, if channel 0 has been configured to operate in the e3 mode, then t he user is expected to apply a 34.368mhz clock signal to this input pin. note: for more information on using the xrt94l33 for atm uni/ppp applications, t he user should consult the xrt94l33 1-channel sts-3c/3-channel ds3/e3/sts-1 atm uni/ppp data sheet. b20 txds3clk_1 txe3clk_1 i ttl transmit ds3/e3 reference clock input ? channel 1 (not used for mapper applications): the exact manner in which the user should handle this input pin depends upon whether channel 1 has been configured to operate in the mapper mode or in the atm uni/ppp mode. if channel 1 is configured to operate in the mapper mode : if channel 1 has been configured to operate in the mapper mode, then this input pin supports no function, and should, therefore, be connected to gnd. if channel 1 is configured to operate in the atm uni/ppp mode: if channel 1 (within the xrt94l33) has been configured to operate in the atm uni/ppp mode, then this input pin will function as the timing reference clock signal for the transmit sts-1/ds3/e3 framer block circ uitry, provided that channel 1 has been configured to operate in the local timing mode. if channel 1 has been configured to operate in the ds3 mode, then the user is expected to apply a 44.736mhz clock signal to this input pin. likewise, if channel 1 has been configured to operate in the e3 mode, then t he user is expected to apply a 34.368mhz clock signal to this input pin. note: for more information on using the xrt94l33 for atm uni/ppp applications, t he user should consult the xrt94l33 1-channel sts-3c/3-channel ds3/e3/sts-1 atm uni/ppp data sheet.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 33 af17 txds3clk_2 txe3clk_2 i ttl transmit ds3/e3 reference clock input ? channel 2 (not used for mapper applications): the exact manner in which the user should handle this input pin depends upon whether channel 2 has been configured to operate in the mapper mode or in the atm uni/ppp mode. if channel 2 is configured to operate in the mapper mode : if channel 2 has been configured to operate in the mapper mode, then this input pin supports no function, and should, therefore, be connected to gnd. if channel 2 is configured to operate in the atm uni/ppp mode: if channel 2 (within the xrt94l33) has been configured to operate in the atm uni/ppp mode, then this input pin will function as the timing reference clock signal for the transmit sts-1/ds3/e3 framer block circ uitry, provided that channel 2 has been configured to operate in the local timing mode. if channel 2 has been configured to operate in the ds3 mode, then the user is expected to apply a 44.736mhz clock signal to this input pin. likewise, if channel 2 has been configured to operate in the e3 mode, then t he user is expected to apply a 34.368mhz clock signal to this input pin. note: for more information on using the xrt94l33 for atm uni/ppp applications, t he user should consult the xrt94l33 1-channel sts-3c/3-channel ds3/e3/sts-1 atm uni/ppp data sheet. b11 a22 ad16 txohclk_0 txohclk_1 txohclk_2 o cmos transmit overhead clock output: this output pin functions as the ?transmit overhead clock? output for the transmit system side interface when the xrt94l33 is configured to oper ate in sts-1/ds3/e3 mode, however, it functions as the ?transmit sts-1 overhead? clock output when the device is confi gured to operate in the sts-1 mode. when configured to operate in ds3/e3 mode: this output pin functions as the ?transmit overhead data input interface clock signal. if the user enables the ?transmit overhead data input interfac e? block by asserting the ?txohins? input pin, then the transmit overhead data input interface block will sample and latch the data (residing on the ?txoh_n? input pin) upon the falling edge of this signal. when configured to operate in sts-1 mode: these output pins, along with ?txoh_n?, ?txohenable_n?, ?txohins_n? and ?txohframe? func tion as the ?transmit path overhead (txoh) input port?. the ?txohframe? and ?txohenable? output pins are updated upon the falling edge this clock output signal. the ?txohins_n? input pins and th e data residing on the ?txoh_n? input pins are sampled upon the falling edge of this clock signal.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 34 d12 c18 ac16 txohenable_0 txohenable_1 txohenable_2 o cmos transmit overhead enable output indicator this output pin functions as the ?transmit overhead enable? output indicator for the transmit system side interface when the xrt94l33 is configured to oper ate in sts-1/ds3/e3 mode, however, it functions as the ?transmit sts-1 overhead enable? output when the device is configured to operate in the sts-1 mode. when configured to operate in ds3/e3 mode: the channel will assert this output pin, for one ?txinclk? period, just prior to the inst ant that the transmit overhead data input interface will be sampling and processing an overhead bit. if the local terminal equipment intends to insert its own value for an overhead bit, into the outbound ds3 or e3 data stream, then it is expected to sample t he state of this signal, upon the falling edge of ?txinclk?. upon sampling the ?txohenable_n? signal high, the local terminal equipment should (1) place the desired value of the overhead bi t, onto the ?txoh_n? input pin and (2) assert the ?txohins_n? input pin. the transmit overhead data input interface block will sample and latch the data on the ?txoh_n? signal, upo n the rising edge of the very next ?txinclk_n? input signal. when configured to operate in sts-1 mode: these output pins, along with ?txoh_n?, ?txohins_n?, ?txohframe_n? and ?txohclk_n? function as the ?transmit path overhead (txoh) input port?. these output pins will pulse ?hig h? anytime the ?txoh? port is ready to accept and process poh bytes. these output pins will be ?low? at all other times.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 35 e12 e17 ab16 txoh_0 txoh_1 txoh_2 i ttl transmit overhead data input: this input pin functions as the ?transmit overhead data? output indicator for the transmit system side interface when the xrt94l33 is configured to oper ate in sts-1/ds3/e3 mode, however, it functions as the ?transmit sts-1 overhead enable? output when the device is configured to operate in the sts-1 mode. when configured to operate in ds3/e3 mode: the transmit overhead data input interface accepts overhead via these input pins, and insert th is data into the ?overhead? bit positions within the outbound ds3 or e3 frames. if the ?txohins_n? input pin is pulled ?high?, then the transmit overhead data input interface will sample the overhead data, via this input pin, upon the falling edge of the txohclk_n output signal. conversely, if the txohins_n input pin is not pulled ?high?, then the transmit overhead data input interface block will be inactive and will not accept any overhead data via the txoh_n input pin. when configured to operate in sts-1 mode: these input pins permit the user to do the following. 1. to insert the poh data into each of the 3 transmit sts-1 poh processor blocks (for insertion and transmission via each of the ?outbound? sts-1 signals). 2. to insert the toh data into each of the 3 transmit sts-1 toh processor blo cks (for insertion and transmission via each of the ?outbound? sts-1 signals). the exact function of these input pins, depend upon whether the user have opted to insert the toh data into the 3 transmit sts-1 toh processor blocks, or not.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 36 e12 e17 ab16 txoh_0 txoh_1 txoh_2 i ttl continued if the user is only inserting poh data via these input pins: in this mode, the external circuitry (which is being interfaced to the ?transmit path overhead input port? is suppose to monitor the following output pins. ? txohframe_n ? txohenable_n ? txohclk_n the ?txohframe_n? output pin will toggle ?high? upon the falling edge of ?txohclk_n? appr oximately one ?txohclk_n? period prior to the ?txoh? port being ready to accept and process the first bit within j1 by te (e.g., the first poh byte). the ?txohframe_n? output pin will remain ?high? for eight consecutive ?txohclk_n? periods. the external circuitry should use this pin to note sts-1 spe frame boundaries. the ?txohenable_n? output pin will toggle ?high? upon the falling edge of ?txohclk_n? appr oximately one ?txohclk_n? period prior to the ?txoh? port being ready to accept and process the first bit within a given poh byte. if the user wishes to externally insert a given poh byte; (1) assert the ?txohins_n? input pin by toggling it ?high?, and (2) place the value of the first bit (within this particular poh byte) on this input pin upon the very next falling edge of ?txohclk_n?. this data bit will be sampled upon the very next falling edge of ?txohclk_n?. the external circuitry should continue to keep the ?txohins_n? input pin ?high? and advancing the next bits (within the poh bytes) upon each rising edge of ?txohclk_n?.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 37 e12 e17 ab16 txoh_0 txoh_1 txoh_2 i ttl continued if the user is inserting both poh and toh data via these input pins: in this mode, the external circuitry (which is being interfaced to the ?transmit path overhead input port? is suppose to monitor the following output pins. ? txohframe_n ? txohenable_n ? txohclk_n the ?txohframe_n? output pin will toggle ?high? twice during a given sts-1 frame period. first, this output pin will toggle high coincident with the ?txoh? port being ready to accept and process the a1 byte (e.g., the ve ry first toh byte). second, this output pin will toggle ?high? coincident with the ?txoh? port being ready to accept and process the j1 byte (e.g., the very first poh byte). if the externally circ uitry samples the ?txohframe_n? output pin ?high?, and the ?txohenable _n? output pin ?low?, then the ?txoh? port is now ready to accept and process the very first toh byte. if the externally circ uitry samples the ?txohframe_n? output pin ?high? and the ?txohenable_n? output pin ?high?, then the ?txoh? port is now ready to accept and process the very first poh byte. to externally insert a given poh or toh byte; (1) assert the ?txohins_n? input pin by toggling it ?high?, and (2) place the value of the first bit (within this particular poh or toh byte) on this input upon the very next falling edge of ?txohclk_n? this data bit will be sampled upon the very next falling edge of ?txohclk_n?. the external circuitry should continue to keep the ?txohins_n? input pin ?high? and advancing the next bits (within the poh bytes) upon each rising edge of ?txohclk_n?.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 38 f12 b19 ag19 txohins_0 txohins_1 txohins_2 i ttl transmit overhead data insert input: this input pin functions as the ?transmit overhead data insert? input indicator for the transmit system side interface when the xrt94l33 is configured to operate in sts-1/ds3/e3 mode, however, it functions as the ?transmit sts-1 overhead enable? output when the device is configured to operate in the sts-1 mode. when configured to operate in ds3/e3 mode: this input pin permits the user to either enable or disable the ?transmit overhead data input interface? block within the ds3/e3 frame generator block. if the transmit overhead data input interface block is enabled, then the ds3/e3 frame generator block will accept overhead data (from the local terminal equipment) via the ?txoh_n? input pin; and insert th is data into the overhead bit positions within the outbound ds3 or e3 data stream. conversely, if the transmit overhead data input interface block is disabled, then the ds 3/e3 frame generator block it will not accept overhead data from the local terminal equipment. pulling this input pin ?high? enables the ?transmit overhead data input interface? block. pulling this input pin ?low? disables the ?transmit overhead data input interface? block when configured to operate in sts-1 mode: these input pins, along with ?txoh_n?, ?txohenable_n?, ?txohframe_n? and ?txohclk_n? function as the ?transmit overhead (txoh) input port. these input pins permit the user to enable or disable the ?txoh? input port. if these input pins are pulled ?hig h?, then the ?txoh? port will sample and latch data via the corresponding ?txoh? input pins, upon the falling edge of ?txohclk_n?. conversely, if these input pins are pulled ?low?, then the ?txoh? port will not sample and latch data via the corresponding ?txoh? input pins. note: if the ?txohins_n? input pin is pulled ?low?, this setting will be overridden if the user has configured the ?transmit sonet/sts-1 poh processor? or ?transmit sts-1 toh processor? blocks to accept certain poh or toh overhead bytes via the external port.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 39 a9 d17 af18 txohframe_0 txohframe_1 txohframe_2 o cmos transmit overhead framing pulse: this input pin functions as th e ?transmit overhead framing? pulse for the transmit system side interface when the xrt94l33 is configured to operat e in ds3/e3 mode, however, it functions as the ?transmit sts-1 overhead enable? output when the device is configured to operate in the sts-1 mode. when configured to operate in ds3/e3 mode: this output pin pulses high (for one txohclk_n? period) coincident with the instant t hat the ds3/e3 frame generator block will be accepting the very first overhead bit within an outbound ds3 or e3 frame (via transmit overhead data input interface). when configured to operate in sts-1 mode: these output pins, along with the ?txoh_n?, ?txohenable_n?, ?txohins_n? and ?txohclk_n? function as the ?transmit overhead input port?. the exact function of these out put pins depends upon whether the user inserting poh or to h data via the ?txoh_n? input pins. if the user is only inserting poh data via these input pins: in this mode, the ?txoh? port will pulse these output pins ?high? whenever it is ready to accept and process the j1 byte (e.g., the very first poh byte) via this port. if the user is inserting both poh and toh data via these input pins: in this mode, the ?txoh? port will pulse these output pins ?high? coincident with the following. whenever the ?txoh? port is ready to accept and process the a1 byte (e.g., the very fi rst toh byte) via this port. whenever the ?txoh? port is ready to accept and process the j1 byte (e.g., the very fi rst poh byte) via this port. notes: 1. the externally circuitry can determine whether the ?txoh? port is expecting the a1 byte or the j1 byte, by checking the state of the corresponding ?txohenable? output pin. if the ?txohenable_n? output pin is ?low? while the ?txohframe_n? output pin is ?high?, then the ?txoh? port is ready to process the a1 (toh) bytes. 2. if the ?txohenable_n? output pin is ?high? while the ?txohframe_n? output pin is ?high?, then the ?txoh? port is ready to process the j1 (poh) bytes.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 40 af19 ag21 ae17 stuffcntl_0/ txhdlc_clk_0/ stuffcntl_1/ txhdlc_clk_1/ stuffcntl_2/ txhdlc_clk_2/ i/o ttl/cmos transmit plcp processor block ? nibble trailer stuff control input pin/transmit high-speed hdlc controller input interface ? clock output pin ? channel n: the exact function of this input pin depends upon (1) whether the xrt94l33 has been configured to operate in the atm uni/plcp mode and (2) whether a given ds3/e3 framer block/channel has been configured to operate in the ?high- speed hdlc controller? mode, as described below. atm uni mode - stuffcnt_n: transmit plcp processor block nibble-trailer stuff control input pin ? channel n - stuffcnt_n: this pin only functions in this particular role if the xrt94l33 has been configured to operate in the atm uni mode. for more information on this pin operating in this mode, please see the xrt94l33 pin description for atm uni/ppp applications. high-speed hdlc controller mode ? transmit hdlc controller input interace block - clock output signal ? channel n ? txhdlcclk_n: this output signal functions as the ?demand? clock for the transmit high-speed hdlc controller input interface block, associated with the ds3/e3 framer blocks. whenever the user pulls the ?snd_msg_n? input pin ?high? then the transmit high-speed hdlc controller block will begin to sample and latch the contents of the ?txhdlcdat[7:0] input pins upon the falling edge of this clock signal. the user is advised to configure their terminal equipment circuitry to output (or place) data onto the ?txhdlcdat[7:0] bus upon the rising edge of this clock signal. since the transmit hdlc controller block is sampling and latching 8-bits of data at a giv en time, it may be assumed that the frequency of the txhdlc_clk _n output signal is either 34.368mhz/8 or 44.736mhz/8. in general, this presumption is true. however, because the transmit hdlc controller block is also performing ?zero-stuffi ng? of the user data that it accepts from the terminal equipment, the frequency of this signal may be slower. note: the user should tie this pin to gnd if the ds3/e3 framer block has not been configured to operate in the ?high-speed hdlc controller? mode.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 41 ac17 ad17 ag20 eightkhzsync_0/ rxhdlc_clk_0/ eightkhzsync_1/ rxhdlc_clk_1/ eightkhzsync_2/ rxhdlc_clk_2/ i/o ttl/cmos transmit plcp processor block ? 8khz framing alignment input/receive high-speed hdlc controller output interface block ? clock output ? channel n: the exact function of this input pin depends upon (1) whether the xrt94l33 has been configured to operate in the atm uni/plcp mode and (2) whether channel n has been configured to operate in the ?high-speed hdlc controller? mode, as described below. atm uni mode - eightkhzsync_n: transmit plcp processor block 8khz framing alignment input: this pin only functions in this particular role if the xrt94l33 has been configured to operate in the atm uni mode. for more information on this pin operating in this mode, please see the xrt94l33 pin description for atm uni/ppp applications. high-speed hdlc controller mode - receive high-speed hdlc controller output interface block - clock output signal ? channel n ? rxhdlcclk_n: this output pin functions as the ?receive high-speed hdlc controller output interface block ? clock output signal for channel n. the receive high-speed hdlc controller output interface block outputs the cont ents of all received hdlc frames and flag sequence octets via the receive high-speed hdlc controller output interface block ? data bus output pins (rxhdlcdat_n[7:0]) upon the rising edge of this clock signal. the user is advised to configure the terminal equipment to sample the contents of the rxhdlcdat_n[7:0] output pins upon the falling edge of this clock signal. note: the user should tie this pin to gnd if the ds3/e3 framer block has not been configured to operate in the ?high-speed hdlc controller? mode. d27 txperr i ttl for mapper applications, please connect this pin to gnd. g25 txpeop i ttl for mapper applications, please connect this pin to gnd. f25 txmod_0 i ttl for mapper applications, please connect this pin to gnd. j24 txuprty/ txpprty i ttl for mapper applications, please connect this pin to gnd.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 42 h27 g27 l24 j26 l23 k25 f27 h26 g26 k24 j25 e27 k23 f26 h25 e26 txudata_0/ txpdata_0 txudata_1/ txpdata_1 txudata_2/ txpdata_2 txudata_3/ txpdata_3 txudata_4/ txpdata_4 txudata_5/ txpdata_5 txudata_6/ txpdata_6 txudata_7/ txpdata_7 txudata_8/ txpdata_8 txudata_9/ txpdata_9 txudata_10/ txpdata_10 txudata_11/ txpdata_11 txudata_12/ txpdata_12 txudata_13/ txpdata_13 txudata_14/ txpdata_14 txudata_15/ txpdata_15 i ttl for mapper applications, pleas e connect these input pins to gnd. m24 m23 j27 k26 l25 txuaddr_0 txuaddr_1 txuaddr_2 txuaddr_3 txuaddr_4 i ttl for mapper applications, pleas e connect these input pins to gnd. l26 txuclav/txppa o cmos for mapper applications, please leave this pin open. m25 txusoc/ txpsop/ txpsoc i ttl for mapper applications, please connect this pin to gnd. k27 txtsx / txpsof i ttl for mapper applications, please connect this pin to gnd. m26 txuenb_l/ txpenb_l i ttl for mapper applications, please connect this pin to vdd. l27 txuclko/ txpclko o cmos for mapper applications, please leave this pin open. m27 txuclk/ txpclk i ttl for mapper applications, please connect this pin to gnd.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 43 sts-1 t elecom b us i nterface ? t ransmit d irection
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 44 c14 sts1txa_ck_0 txsendfcs_0 txgfcclk_0 i i o ttl ttl cmos sts-1 transmit telecom bus clock input pin/transmit hdlc control block send fcs command input pin ? channel 0: the exact function of this input pin depends upon whether the sts-1 telecom bus interface for channel 0 has been enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts1txa_clk_0 - ?sts-1 transmit telecom bus? transmit clock input ? channel 0: this input clock signal functions as the clock source for the sts-1 transmit telecom bus, associated with channel 0. all input signals (e.g., sts1txa_alarm_0, sts1txa_d_0[7:0], sts1txa_dp_0, sts1txa_pl_0, sts1txa_c1j1_0) are sampled upon the falling edge of this input clock signal. this clock signal should operate at 19.44mhz. (for sts-3 mode) or 6.48mhz (for sts-1 mode) if sts-1 telecom bus (channel 0) has not been enabled: if sts-1 telecom bus (channel 0) has not been enabled, then this particular pin can be configured to function in either of the following roles. txsendfcs_0 (transmit hdl c controller block send fcs command input ? high speed hdlc controller mode only) the user?s terminal equipment is expected to control both this input pin and the ?txsendmsg_0? input pin during the construction and transmission of each outbound hdlc frame. this input pin permits the user to command the transmit hdlc controller block to compute and insert the computed fcs value into the back-end of the ?outbound? hdlc frame as a trailer. if the user has configured the transmit hdlc controller to compute and insert a crc-16 value into the ?outbound? hdlc frame, then the terminal equipment is expected to pull this input pin ?high? for two periods of txhdlcclk_0. likewise, if the user has configured the transmit hdlc controller to compute and insert a crc-32 value into the ?outbound? hdlc frame, then the terminal equipment is expected to pull this input pin ?high? for four periods of txhdlcclk_0. txgfcclk_0 (transmit gfc nibble-field input port clock signal input) ? atm applications only. this pin only functions in this particular role if the xrt94l33 has been configured to operate in the atm uni mode. note: the user should tie this pin to gnd the ds3/e3 framer block has not been configured to operate in the ?high-speed hdlc controller? mode.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 45 e19 sts1txa_ck_1 txsendfcs_1 txgfcclk_1 i i o ttl ttl cmos sts-1 transmit telecom bus clock input pin/transmit hdlc control block send fcs command input pin ? channel 1: the exact function of this input pin depends upon whether the sts-1 telecom bus interface for channel 1 has been enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts1txa_clk_1 - ?sts-1 transmit telecom bus? clock input ? channel 1: this input clock signal functions as the clock source for the sts-1 transmit telecom bus, associated with channel 1. all input signals, (e.g., sts1txa_alarm_1, sts1txa_d_1[7:0], sts1txa_dp_1, sts1txa_pl_1, sts1txa_c1j1_1) are sampled upon the falling edge of this input clock signal. this clock signal should operate at 19.44mhz. (for sts-3 mode) or 6.48mhz (for sts-1 mode) if sts-1 telecom bus (channel 1) has not been enabled: if sts-1 telecom bus (channel 1) has not been enabled, then this particular pin can be configured to function in either of the following roles. txsendfcs_1 (transmit hdl c controller block send fcs command input ? high speed hdlc controller mode only) the user?s terminal equipment is expected to control both this input pin and the ?txsendmsg_1? input pin during the construction and transmission of each outbound hdlc frame. this input pin permits the user to command the transmit hdlc controller block to compute and insert the computed fcs value into the back-end of the ?outbound? hdlc frame as a trailer. if the user has configured the transmit hdlc controller to compute and insert a crc-16 value into the ?outbound? hdlc frame, then the terminal equipment is expected to pull this input pin ?high? for two periods of txhdlcclk_1. likewise, if the user has configured the transmit hdlc controller to compute and insert a crc-32 value into the ?outbound? hdlc frame, then the terminal equipment is expected to pull this input pin ?high? for four periods of txhdlcclk_1. txgfcclk_1 (transmit gfc nibble-field input port clock signal input) ? atm applications only. this pin only functions in this particular role if the xrt94l33 has been configured to operate in the atm uni mode. note: the user should tie this pin to gnd if the ds3/e3 framer block has not been configured to operate in the ?high-speed hdlc controller? mode.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 46 ac14 sts1txa_ck_2 txsendfcs_2 txgfcclk_2 io ttl cmos cmos sts-1 transmit telecom bus clock input pin/transmit hdlc control block send fcs command input pin ? channel 2: the exact function of this input pin depends upon whether the sts-1 telecom bus interface for channel 2 has been enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts1txa_clk_2 ? ?sts-1 transmit telecom bus? transmit clock input ? channel 2: this input clock signal functions as the clock source for the sts-1 transmit telecom bus, associated with channel 2. all input signals, (e.g., sts1txa_alarm_2, sts1txa_d_2[7:0]?, sts1txa_dp_2, sts1txa_pl_2, sts1txa_c1j1_2) are sampled upon the falling edge of this input clock signal. this clock signal should operate at 19.44mhz. (for sts-3 mode) or 6.48mhz (for sts-1 mode) if sts-1 telecom bus (channel 1) has not been enabled: if sts-1 telecom bus (channel 1) has not been enabled, then this particular pin can be configured to function in either of the following roles. txsendfcs_2 (transmit hdl c controller block send fcs command input ? high speed hdlc controller mode only) the user?s terminal equipment is expected to control both this input pin and the ?txsendmsg_2? input pin during the construction and transmission of each outbound hdlc frame. this input pin permits the user to command the transmit hdlc controller block to compute and insert the computed fcs value into the back-end of the ?outbound? hdlc frame as a trailer. if the user has configured the transmit hdlc controller to compute and insert a crc-16 value into the ?outbound? hdlc frame, then the terminal equipment is expected to pull this input pin ?high? for two periods of txhdlcclk_2. likewise, if the user has configured the transmit hdlc controller to compute and insert a crc-32 value into the ?outbound? hdlc frame, then the terminal equipment is expected to pull this input pin ?high? for four periods of txhdlcclk_2. txgfcclk_2 (transmit gfc nibble-field input port clock signal input) ? atm applications only. this pin only functions in this particular role if the xrt94l33 has been configured to operate in the atm uni mode. note: the user should tie this pin to gnd if the ds3/e3 framer block has not been configured to operate in the ?high-speed hdlc controller? mode.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 47 e14 sts1txa_pl_0 txsendmsg_0 i ttl sts-1 transmit telecom bus ? payload indicator signal input/transmit hdlc controller block send message command input pin ? channel 0: the exact function of this input depends upon whether the sts-1 telecom bus interface for channel 0 has been enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts1txa_pl_0 - sts-1 transmit telecom bus ? payload indicator signal ? channel 0: this input pin indicates whether or not ?transport overhead? (toh) bytes are being input via the ?txa_d_0[7:0]? input pins. this input pin should be pulled ?low? for the duration that the ?sts-1 transmit telecom bus is receiving a toh byte, via the ?txa_d_0[7:0]? input pins. conversely, this input pin should be pulled ?high? at all other times. note: this input signal is sampled upon the falling edge of ?sts1txa_ck_0?. if sts-1 telecom bus (channel 0) has not been enabled: if sts-1 telecom bus (channel 0) has not been enabled, then this particular pin can either be configured to function as the ?txsendmsg_0? input pin (if the ds3/e3 framer block within channel 0 has been configured to operate in the ?high-speed hdlc controller mode), or the user should simply tie this input pin to gnd. the details of this pin?s role as the ?txsendmsg_0? input pin is described below. txsendmsg_0 (transmit hdlc controller block send message command input ? high speed hdlc controller mode only) this input pin permits the user to command the transmit hdlc controller block (associated with channel 0) to begin sampling and latching the data which is being applied to the ?txhdlcdat_0[7:0]? input pins. if the user pulls this input pin ?high?, then the transmit hdlc controller block samples and latches the data which is applied to the ?txhdlcdat_0[7:0]? input pins upon the rising edge of ?txhdlcclk_0?. each byte of th is sampled data will ultimately be encapsulated into an outbound hdlc frame and will be mapped into the payload bits within the outbound ds3/e3 frames via the ds3/e3 frame generator block. if the user pulls this input pin ?low? then the transmit hdlc controller block will not sample and latch the contents on the ?txhdlcdat_0[7:0]? input pins, and the transmit hdlc controller block will simply generate a continuous stream of flag sequence octets (0x7e). note: the user should tie this pin to gnd if the ds3/e3 framer block has not been configured to operate in the ?high-speed hdlc controller? mode.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 48 c22 sts1txa_pl_1 txsendmsg_1: i ttl sts-1 transmit telecom bus ? payload indicator signal input/transmit hdlc controller block send message command input pin ? channel 1: the exact function of this input pin depends upon whether the sts-1 telecom bus interface for channel 1 has been enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts1txa_pl_1 - sts-1 transmit telecom bus ? payload indicator signal ? channel 1: this input pin indicates whether or not ?transport overhead? (toh) bytes are being input via the ?txa_d_1[7:0]? input pins. this input pin should be pulled ?low? for the duration that the sts-1 transmit telecom bus is receiving a toh byte, via the ?txa_d_1[7:0]? input pins. conv ersely, this input pin should be pulled ?high? at all other times. note: this input signal is sampled upon the falling edge of ?sts1txa_ck_1?. if sts-1 telecom bus (channel 1) has not been enabled: if sts-1 telecom bus (channel 1) has not been enabled, then this particular pin can either be configured to function as the ?txsendmsg_1? input pin (if the ds3/e3 framer block within channel 1 has been configured to operate in the ?high-speed hdlc controller mode), or the user should simply tie this input pin to gnd. the details of this pin?s role as the ?txsendmsg_1? input pin is described below. txsendmsg_1 (transmit hdlc controller block send message command input ? high speed hdlc controller mode only) this input pin permits the user to command the transmit hdlc controller block (associated with channel 1) to begin sampling and latching the data which is being applied to the ?txhdlcdat_1[7:0]? input pins. if the user pulls this input pin ?high?, then the transmit hdlc controller block samples and latches the data which is applied to the ?txhdlcdat_1[7:0]? input pins upon the rising edge of ?txhdlcclk_1?. each byte of this sampled data will ultimately be encapsulated into an outbound hdlc frame and will be mapped into the payload bits within the outbound ds3/e3 frames via the ds3/e3 frame generator block. if the user pulls this input pin ?low? then the transmit hdlc controller block will not sample and latch the contents on the ?txhdlcdat_1[7:0]? input pins, and the transmit hdlc controller block will simply generate a continuous stream of flag sequence octets (0x7e). note: the user should tie this pin to gnd if the ds3/e3 framer block has not been configured to operate in the ?high-speed hdlc controller? mode.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 49 ad14 sts1txa_pl_2 txsendmsg_2: i ttl sts-1 transmit telecom bus ? payload indicator signal input/transmit hdlc controller block send message command input pin ? channel 2: the exact function of this input pin depends upon whether the sts-1 telecom bus interface for channel 2 has been enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 transmit telecom bus ? payload indicator signal ? channel 2: this input pin indicates whether or not ?transport overhead? (toh) bytes are being input via the ?txa_d_2[7:0]? input pins. this input pin should be pulled ?low? for the duration that the sts-1 transmit telecom bus is receiving a toh byte, via the ?txa_d_2[7:0]? input pins. conv ersely, this input pin should be pulled ?high? at all other times. note: this input signal is sampled upon the falling edge of ?sts1txa_ck_2?. if sts-1 telecom bus (channel 2) has not been enabled: if sts-1 telecom bus (channel 2) has not been enabled, then this particular pin can either be configured to function as the ?txsendmsg_2? input pin (if the ds3/e3 framer block within channel 2 has been configured to operate in the ?high-speed hdlc controller mode), or the user should simply tie this input pin to gnd. the details of this pin?s role as the ?txsendmsg_2? input pin is described below. txsendmsg_2 ( transmit hdlc controller block send message command input ? high speed hdlc controller mode only) this input pin permits the user to command the transmit hdlc controller block (associated with channel 2) to begin sampling and latching the data which is being applied to the ?txhdlcdat_2[7:0]? input pins. if the user pulls this input pin ?high?, then the transmit hdlc controller block samples and latches the data which is applied to the ?txhdlcdat_2[7:0]? input pins upon the rising edge of ?txhdlcclk_2?. each byte of this sampled data will ultimately be encapsulated into an outbound hdlc frame and will be mapped into the payload bits within the outbound ds3/e3 frames via the ds3/e3 frame generator block. if the user pulls this input pin ?low? then the transmit hdlc controller block will not sample and latch the contents on the ?txhdlcdat_2[7:0]? input pins, and the transmit hdlc controller block will simply generate a continuous stream of flag sequence octets (0x7e). note: the user should tie this pin to gnd if the ds3/e3 framer block has not been configured to operate in the ?high-speed hdlc controller? mode.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 50 d14 sts1txa_c1j1_0 rxds3lineclk_0 i ttl sts-1 transmit telecom bus c1/j1 byte phase indicator input signal/receive ds3/e3/sts-1 clock input from liu (channel 0): the exact function of this pin depends upon whether the sts- 1 telecom bus interface for channel 0 has been enabled or not. if sts-1 telecom bus (channel 0) has been enabled - sts- 1 transmit telecom bus c1/j1 byte phase indicator input signal (channel 0): this input pin should be pulsed ?high? during both of the following conditions. whenever the c1 byte is being input to the sts-1 transmit telecom bus (txa_d_0[7:0]) input pins. whenever the j1 byte is being input to the sts-1 transmit telecom bus (txa_d_0[7:0]) input pins. this input pin should be pulled ?low? at all other times. if sts-1 telecom bus (channel 0) has not been enabled - rxds3lineclk_0 (receive ds3/e3/sts-1 clock input from liu) the ds3/e3 framer block and the receive sts-1 toh processor block (associated with channel 0) uses this input pin to sample and latch the data that is present on the rxds3pos_0 and rxds3neg_0 (f or dual-rail operation only) inputs. this input clock signal also functions as the timing source for the ingress direction signal and circuitry within the ds3/e3 framer block of channel 0. the user is expected to connect this input to the recovered clock output of a ds3/e3/sts-1 liu ic.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 51 a24 sts1txa_c1j1_1 rxds3lineclk_1/ rxsts1lineclk_1 i ttl transmit sts-1 telecom bus interface - c1/j1 byte phase indicator input signal ? channel 1/receive ds3/e3/sts-1 clock input from liu ? channel 1: the exact function of this pin depends upon whether the sts- 1 telecom bus interface for channel 1 has been enabled or not. if the sts-1 telecom bus (channel 1) has been enabled - transmit sts-1 telecom bus interface - c1/j1 byte phase indicator input signal (channel 1): this input pin should be pulsed ?high? during both of the following conditions. whenever the c1 byte is being input to the transmit sts-1 telecom bus interface input pins (txa_d_1[7:0]). whenever the j1 byte is being input to the transmit sts-1 telecom bus interface input pins (txa_d_1[7:0]). this input pin should be pulled ?low? at all other times. if the sts-1 telecom bus (channel 1) has not been enabled - rxds3lineclk_1 (receive ds3/e3/sts-1 clock input from liu) the ds3/e3 framer block and the receive sts-1 toh processor block (associated with channel 1) uses this input pin to sample and latch the data that is present on the rxds3pos_1 and rxds3neg_1 (f or dual-rail operation only) inputs. this input clock signal also functions as the timing source for the ingress direction signal and circuitry within the ds3/e3 framer block of channel 1. the user is expected to connect this input to the recovered clock output pin of an off chip ds3/e3/sts-1 liu ic.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 52 af14 sts1txa_c1j1_2 rxds3lineclk_2 i ttl sts-1 transmit telecom bus c1/j1 byte phase indicator input signal/receive ds3/e3/sts-1 clock input from liu (channel 2): the exact function of this pin depends upon whether the sts- 1 telecom bus interface for channel 2 has been enabled or not. if sts-1 telecom bus (channel 2) has been enabled - sts- 1 transmit telecom bus c1/j1 byte phase indicator input signal (channel 2): this input pin should be pulsed ?high? during both of the following conditions. whenever the c1 byte is being input to the sts-1 transmit telecom bus (txa_d_2[7:0]) input pins. whenever the j1 byte is being input to the sts-1 transmit telecom bus (txa_d_2[7:0]) input pins. this input pin should be pulled ?low? at all other times. is sts-1 telecom bus (channel 2) has not been enabled - rxds3lineclk_2 (receive ds3/e3/sts-1 clock input from liu) the ds3/e3 framer block and the receive sts-1 toh processor block (associated with channel 2) uses this input pin to sample and latch the data that is present on the rxds3pos_2 and rxds3neg_2 (f or dual-rail operation only) inputs. this input clock signal also functions as the timing source for the ingress direction signal and circuitry within the ds3/e3 framer block of channel 2. the user is expected to connect this input to the recovered clock output of a ds3/e3/sts-1 liu ic.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 53 b14 sts1txa_dp_0 rxds3pos_0 i ttl sts-1 transmit telecom bus ? parity input pin/receive ds3/e3/sts-1 positive-polarity data input from liu ? channel 0: the exact function of this pin depends upon whether the sts- 1 telecom bus interface for channel 0 has been enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts1txa_dp_0 - sts-1 transmit telecom bus interface # 0 ? parity input pin: this input pin can be configured to function as one of the following. the even or odd parity value of the bits which are input via the ?sts1txa_d_0[7:0]? input pins. the even or odd parity value of the bits which are being input via the ?sts1txa_d_0[7:0]? input, and the states of the ?sts1txa_pl_0? and ?sts1txa_c1j1_0? input pins. note: the user can make any o ne of these configuration selections by writing the appropriate value into the ?interface control register ? byte 0? register (address location = 0x013b). if sts-1 telecom bus (channel 0) has not been enabled - rxds3pos_0 (receive ds3/e3/sts-1 positive-polarity data input from liu) the ds3/e3 framer block and the receive sts-1 toh processor block (associated with channel 0) will sample the data being applied to this input pin upon the user-selected edge of the ?rxds3lineclk_0? input signal. if the user has configured channel 0 to operate in the sts-1 mode, or in the single-rail mode (if also configured to operate in the ds3/e3 mode), then all recovered ds3, e3 or sts-1 data (from the ds3/e3/sts-1 liu ic) should be applied to this input pin. if the user has configured channel 0 to operate in both the ds3/e3 and the dual-rail mode, then only the ?positive- polarity? portion of the reco vered ds3/e3 data should be applied to this input pin.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 54 c21 sts1txa_dp_1 rxds3pos_1 i ttl sts-1 transmit telecom bus ? parity input pin/receive ds3/e3/sts-1 positive-polarity data input from liu ? channel 1: the exact function of this input pin depends upon whether sts-1 telecom bus interface # 1 has been enable or not. if sts-1 telecom bus (channel 1) has been enabled ? sts1txa_dp_1: sts-1 transmit telecom bus interface # 1 ? parity input pin: this input pin can be configured to function as one of the following. the even or odd parity value of the bits which are input via the ?sts1txa_d_1[7:0]? input pins. the even or odd parity value of the bits which are being input via the ?sts1txa_d_1[7:0]? input and the states of the ?sts1txa_pl_1? and ?sts1txa_c1j1_1? input pins. note: the user can make any one of these configuration selections by writing the appropriate value into the ?interface control register ? byte 1? register (address location = 0x013a). if sts-1 telecom bus (channel 1) has not been enabled - rxds3pos_1 (receive ds3/e3/sts-1 positive-polarity data input from liu ? channel 1) the ds3/e3 framer block and the receive sts-1 toh processor block (associated with channel 1) will sample the data being applied to this input pin upon the user-selected edge of the ?rxds3lineclk_1? input signal. if the user has configured channel 1 to operate in the sts-1 mode, or in the single-rail mode (if also configured to operate in the ds3/e3 mode), then all recovered ds3, e3 or sts-1 data (from the ds3/e3/sts-1 liu ic) should be applied to this input pin. if the user has configured channel 1 to operate in both the ds3/e3 and the dual-rail mode, then only the ?positive- polarity? portion of the reco vered ds3/e3 data should be applied to this input pin.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 55 ag15 sts1txa_dp_2 rxds3pos_2 i ttl sts-1 transmit telecom bus ? parity input pin/receive ds3/e3/sts-1 positive-polarity data input from liu ? channel 2; the exact function of this pin depends upon whether the sts- 1 telecom bus interface for channel 2 has been enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts1txa_dp_2: sts-1 transmit telecom bus interface # 2 ? parity input pin: this input pin can be configured to function as one of the following. the even or odd parity value of the bits which are input via the ?sts1txa_d_2[7:0]? input pins. the even or odd parity value of the bits which are being input via the ?sts1txa_d_2[7:0]? input and the states of the ?sts1txa_pl_2? and ?sts1txa_c1j1_2? input pins. note: the user can make any one of these configuration selections by writing the appropriate value into the ?interface control register ? byte 2? register (address location = 0x0139). if sts-1 telecom bus (channel 2) has not been enabled rxds3pos_2 (receive ds3/e3/sts-1 positive-polarity data input from liu) the ds3/e3 framer block and the receive sts-1 toh processor block (associated with channel 2) will sample the data being applied to this input pin upon the user-selected edge of the ?rxds3lineclk_2? input signal. if the user has configured channel 2 to operate in the sts-1 mode, or in the single-rail mode (if also configured to operate in the ds3/e3 mode), then all recovered ds3, e3 or sts-1 data (from the ds3/e3/sts-1 liu ic) should be applied to this input pin. if the user has configured channel 2 to operate in both the ds3/e3 and the dual-rail mode, then only the ?positive- polarity? portion of the reco vered ds3/e3 data should be applied to this input pin.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 56 a13 sts1txa_alarm_0 rxds3neg_0 rxlcv_0 i ttl transmit sts-1 telecom bus ? alarm indicator input/receive ds3/e3 negative -polarity data input from liu/receive ds3/e3 line code violation input from liu ? channel 0; the exact function of this pin depends upon whether the sts- 1 telecom bus interface for channel 0 has been enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 transmit telecom bus ? alarm indicator input: this input pin pulses ?high? coincident to any sts-1 signal (which is carrying the ais-p indicator) being applied to the sts1txa_d_0[7:0] input data bus. note: if the sts1txa_alarm_0 input signal pulses ?high? for any given sts-1 signal (within the ?incoming? sts-1), then the xrt94l33 will automatically declare the ais-p defect condition for that particular sts-1 channel. if sts-1 telecom bus (channel 0) has not been enabled: if the sts-1 telecom bus (channel 0) has not been enabled, then the role that this particular input pin plays depends upon whether channel 0 is operating in the sts-1 mode, the ds3/e3 single-rail mode or in the ds3/e3 dual- rail mode, as described below. if channel 0 is operating in the sts-1 mode if channel 0 is operating in the sts-1 mode, then the user should tie this pin to gnd. if channel 0 is operating in the ds3/e3 single-rail mode ? receive lcv input from liu if channel 0 is operating in both the ds3/e3 and single-rail modes, then this input pin will function as the lcv (line code violation) input. in this mode, the user is expected to connect the ?lcv? output pin from the liu ic to this input pin. the ds3/e3 framer block will sample this input pin upon the ?user- configured? edge of the ?rxds 3lineclk_0? clock signal, and the primary frame synchronizer block (corresponding with channel 0) will increment the pmon lcv or exz event count registers based upon the data sa mpled at this input pin. if channel 0 is operating in the ds3/e3 dual-rail mode ? receive ds3/e3 negative-polarity data input from liu if the user has configured channel 0 to operate in both the ds3/e3 and the dual-rail mode, then only the ?negative- polarity? portion of the receiv e ds3/e3 data should be applied to this input pin.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 57 d19 sts1txa_alarm_1 rxds3neg_1 rxlcv_1 i ttl transmit sts-1 telecom bus ? alarm indicator input/receive ds3/e3 negative -polarity data input from liu/receive ds3/e3 line code violation input from liu ? channel 1: the exact function of this pin depends upon whether the sts- 1 telecom bus interface for channel 1 has been enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 transmit telecom bus ? alarm indicator input: this input pin pulses ?high? coincident to any sts-1 signal (which is carrying the ais-p indicator) being applied to the sts1txa_d_1[7:0] input data bus. note: if the sts1txa_alarm_1 input signal pulses ?high? for any given sts-1 signal (within the ?incoming? sts-1), then the xrt94l33 will automatically declare the ais-p defect condition for that particular sts-1 channel. if sts-1 telecom bus (channel 1) has not been enabled: if the sts-1 telecom bus (channel 1) has not been enabled, then the role that this particular input pin plays depends upon whether channel 1 is operating in the sts-1 mode, the ds3/e3 single-rail mode or in the ds3/e3 dual- rail mode, as described below. if channel 1 is operating in the sts-1 mode if channel 1 is operating in the sts-1 mode, then the user should tie this pin to gnd. if channel 1 is operating in the ds3/e3 single-rail mode ? receive lcv input from liu if channel 1 is operating in both the ds3/e3 and single-rail modes, then this input pin will function as the lcv (line code violation) input. in this mode, the user is expected to connect the ?lcv? output pin from the liu ic to this input pin. the ds3/e3 framer block will sample this input pin upon the ?user- configured? edge of the ?rxds 3lineclk_1? clock signal, and the primary frame synchronizer block (corresponding with channel 1) will increment the pmon lcv or exz event count registers based upon the data sa mpled at this input pin. if channel 1 is operating in the ds3/e3 dual-rail mode ? receive ds3/e3 negative-polarity data input from liu if the user has configured channel 1 to operate in both the ds3/e3 and the dual-rail mode, then only the ?negative- polarity? portion of the receiv e ds3/e3 data should be applied to this input pin.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 58 af15 sts1txa_alarm_2 rxds3neg_2 rxlcv_2 i ttl transmit sts-1 telecom bus ? alarm indicator input/receive ds3/e3 negative -polarity data input from liu/receive ds3/e3 line code violation input from liu ? channel 2: the exact function of this pin depends upon whether the sts- 1 telecom bus interface for channel 2 has been enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 transmit telecom bus ? alarm indicator input: this input pin pulses ?high? coincident to any sts-1 signal (which is carrying the ais-p indicator) being applied to the sts1txa_d_2[7:0] input data bus. note: if the sts1txa_alarm_2 input signal pulses ?high? for any given sts-1 signal (within the ?incoming? sts-1), then the xrt94l33 will automatically declare the ais-p defect condition for that particular sts-1 channel. if sts-1 telecom bus (channel 2) has not been enabled: if the sts-1 telecom bus (channel 2) has not been enabled, then the role that this particular input pin plays depends upon whether channel 2 is operating in the sts-1 mode, the ds3/e3 single-rail mode or in the ds3/e3 dual- rail mode, as described below. if channel 2 is operating in the sts-1 mode if channel 2 is operating in the sts-1 mode, then the user should tie this pin to gnd. if channel 2 is operating in the ds3/e3 single-rail mode ? receive lcv input from liu if channel 2 is operating in both the ds3/e3 and single-rail modes, then this input pin will function as the lcv (line code violation) input. in this mode, the user is expected to connect the ?lcv? output pin from the liu ic to this input pin. the ds3/e3 framer block will sample this input pin upon the ?user- configured? edge of the ?rxds 3lineclk_2? clock signal, and the primary frame synchronizer block (corresponding with channel 1) will increment the pmon lcv or exz event count registers based upon the data sa mpled at this input pin. if channel 2 is operating in the ds3/e3 dual-rail mode ? receive ds3/e3 negative-polarity data input from liu if the user has configured channel 2 to operate in both the ds3/e3 and the dual-rail mode, then only the ?negative- polarity? portion of the receiv e ds3/e3 data should be applied to this input pin.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 59 b13 sts1txa_d0_0 txhdlcdat_0_0 txgfcmsb_0 i/o ttl/cmos transmit sts-1 telecom bus ? channel 0 ? input data bus pin number 0 the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 0: this input pin along with ?sts1txa_d_0[7:1]? function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 0. this particular input pin functions as the lsb (least significant bit) input pi n on the transmit (add) telecom bus ? input data bus. the st s-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_0?. the lsb of any byte, which is being input into the ?sts-1 transmit telecom bus ? data bus (for channel 0) should be input via this pin. txhdlcdat_0_0 (transmit hdlc block data ? channel 0 ? input data pin 0) if channel 0 has been configured to operate in the ?high- speed hdlc controller? mode, then the system-side terminal equipment will be provided with a ?byte-wide? transmit hdlc controller byte-wide txgfcmsb_0 (transmit gfc msb indicator ? channel 0) ? atm applications only. this pin only functions in this particular role if the xrt94l33 has been configured to operate in the atm uni mode. c13 sts1txa_d1_0 txhdlcdat_1_0 txgfc_0 i ttl transmit sts-1 telecom bus ? channel 0 ? input data bus pin number 1: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 1: this input pin along with ?sts1txa_d_0[7:2]? and ?sts1txa_d0_0 function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 0. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_0?. txhdlcdat_1_0 (transmit hdlc block data ? channel 0 ? input data pin 1) txgfc_0 (transmit gfc data ? channel 0)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 60 d13 sts1txa_d2_0 txhdlcdat_2_0 txcelltxed_0 i ttl/cmos transmit sts-1 telecom bus ? channel 0 ? input data bus pin number 2: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 2: sts1txa_d2_0 this input pin along with ?sts1txa_d_0[7:3]? and ?sts1txa_d_0[1:0] function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 0. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_0?. txhdlcdat_2_0 (transmit hdlc block data ? channel 0 ? input data pin 2) txcelltxed_0 (cell transmitted ? channel 0) e13 sts1txa_d3_0 txhdlcdat_3_0 ssi_clk i/o ttl/cmos transmit sts-1 telecom bus ? channel 0 ? input data bus pin number 3: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 2: sts1txa_d3_0: this input pin along with ?sts1txa_d_0[7:4]? and ?sts1txa_d_0[2:0] function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 0. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_0?. txhdlcdat_3_0 (transmit hdlc block data ? channel 0 ? input data pin 3 ssi_clk (slow speed interface for ingress path clock) a12 sts1txa_d4_0 txhdlcdat_4_0 txds3ohind_0 io ttl/cmos transmit sts-1 telecom bus ? channel 0 ? input data bus pin number 4: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 4: sts1txa_d4_0: this input pin along with ?sts1txa_d_0[7:5]? and ?sts1txa_d_0[3:0] function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 0. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_0?. txhdlcdat_4_0 (transmit hdlc block data ? channel 0 ? input data pin 4) txds3ohind_0 (transmit ds3 overhead indicator ? channel 0)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 61 a11 sts1txa_d5_0 txhdlcdat_5_0 txds3fp_0 i/o ttl/cmos transmit sts-1 telecom bus ? channel 0 ? input data bus pin number 5: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 5: sts1txa_d5_0: this input pin along with ?sts1txa_d_0[7:6]? and ?sts1txa_d_0[4:0] function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 0. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_0?. txhdlcdat_5_0 (transmit hdlc block data ? channel 0 ? input data pin 5) txds3fp_0 (transmit ds3 frame pulse ? channel 0) txsbdata_5_0 b12 sts1txa_d6_0 txhdlcdat_6_0 txds3data_0 txsbdata_6_0 i ttl transmit sts-1 telecom bus ? channel 0 ? input data bus pin number 6: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 6: sts1txa_d6_0: this input pin along with ?sts1txa_d7_0? and ?sts1txa_d_0[5:0]? function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 0. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_0?. if sts-1 telecom bus (channel 0) is disabled ? txhdlcdat_6_0 (transmit hdlc block data ? channel 0 ? input data pin 6) txds3data_0 (transmit ds3 data ? channel 0) txsbdata_6_0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 62 a10 sts1txa_d7_0 txhdlcdat_7_0 txaisen_0 txsbdata_7_0 i ttl transmit sts-1 telecom bus ? channel 0 ? input data bus pin number 7: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 7: sts1txa_d7_0: this input pin along with ?sts1txa_d_0[6:0]? function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 0. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_0?. note: this input pin func tions as the msb (most significant bit) of the transmit (add) telecom bus, for channel 0. if sts-1 telecom bus (channel 0) is disabled ? txhdlcdat_7_0 (transmit hdlc block data ? channel 0 ? input data pin 7) txaisen_0 (transmit ais enable ? channel 0) b23 sts1txa_d0_1 txhdlcdat_0_1 txgfcmsb_1 i/o ttl/cmos transmit sts-1 telecom bus ? channel 1 ? input data bus pin number 0: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 0: this input pin along with ?sts1txa_d_1[7:1]? function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 1. this particular input pin functions as the lsb (least significant bit) input pi n on the transmit (add) telecom bus ? input data bus. the st s-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_1?. the lsb of any byte, which is being input into the ?sts-1 transmit telecom bus ? data bus (for channel 1) should be input via this pin. txhdlcdat_0_1 (transmit hdlc block data ? channel 1 ? input data pin 0) txgfcmsb_1 (transmit gfc msb indicator ? channel 1)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 63 c20 sts1txa_d1_1 txhdlcdat_1_1 txgfc_1 i ttl transmit sts-1 telecom bus ? channel 1 ? input data bus pin number 1: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 1: this input pin along with ?sts1txa_d_1[7:2]? and ?sts1txa_d0_1 function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 1. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_1?. txhdlcdat_1_1 (transmit hdlc block data ? channel 1 ? input data pin 1) txgfc_1 (transmit gfc data ? channel 1) b22 sts1txa_d2_1 txhdlcdat_2_1 txcelltxed_1 i/o ttl/cmos transmit sts-1 telecom bus ? channel 1 ? input data bus pin number 2: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 2: sts1txa_d2_1 this input pin along with ?sts1txa_d_1[7:3]? and ?sts1txa_d_1[1:0] function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 1. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_1?. txhdlcdat_2_1 (transmit hdlc block data ? channel 1 ? input data pin 2) txcelltxed_1 (cell transmitted ? channel 1) e18 sts1txa_d3_1 txhdlcdat_3_1 ssi_pos i/o ttl/cmos transmit sts-1 telecom bus ? channel 1 ? input data bus pin number 3: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 3: sts1txa_d3_1: this input pin along with ?sts1txa_d_1[7:4]? and ?sts1txa_d_1[2:0] function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 1. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_1?. txhdlcdat_3_1 (transmit hdlc block data ? channel 1 ? input data pin 3) ssi_pos (slow speed interface data positive for ingress path)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 64 a23 sts1txa_d4_1 txhdlcdat_4_1 txds3ohind_1 i/o ttl/cmos transmit sts-1 telecom bus ? channel 1 ? input data bus pin number 4: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 4: sts1txa_d4_1: this input pin along with ?sts1txa_d_1[7:5]? and ?sts1txa_d_1[3:0] function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 1. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_1?. if sts-1 telecom bus (channel 1) has not been enabled: if sts-1 telecom bus (channel 1) has not been enabled, then this particular pin can be configured to function in either of the following roles txhdlcdat_4_1 (transmit hdlc block data ? channel 1 ? input data pin 4) this input pin will function as a part of the ?transmit hdlc controller? byte-wide data input bus, whenever the user configures the ds3/e3 framer block (associated with channel 1) to operate in the ?high-spe ed hdlc controller? mode. this pin will function as data input pin # 4. txds3ohind_1 (transmit ds3 overhead indicator ? channel 1) this output pin will pulse ?high? one bit-period prior to the time that the ds3/e3 fram e generator block (within channel 1) will be processing an overhead bit. the purpose of this outpout pin is to warn the terminal equipment that, during the very next bit-period, the ds3/e3 fram e generator block is going to be processing an overhead bit and will be ignoring any data that is applied to to the txser input pin. note: the user can ignore this output pin provide that that either the primary or secondary frame synchronizer block is always ?up-stream? from the ds3/e3 frame generator block.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 65 c19 sts1txa_d5_1 txhdlcdat_5_1 txds3fp_1 i/o ttl/cmos transmit sts-1 telecom bus ? channel 1 ? input data bus pin number 5: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 5: sts1txa_d5_1: this input pin along with ?sts1txa_d_1[7:6]? and ?sts1txa_d_1[4:0] function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 1. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_1?. txhdlcdat_5_1 (transmit hdlc block data ? channel 1 ? input data pin 5) txds3fp_1 (transmit ds3 frame pulse ? channel 1) d18 sts1txa_d6_1 txhdlcdat_6_1 txds3data_1 i ttl transmit sts-1 telecom bus ? channel 1 ? input data bus pin number 6: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 6: sts1txa_d6_1: this input pin along with ?sts1txa_d7_1? and ?sts1txa_d_1[5:0]? function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 1. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_1?. txhdlcdat_6_1 (transmit hdlc block data ? channel 1 ? input data pin 6) txds3data_1 (transmit ds3 data ? channel 1)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 66 b21 sts1txa_d7_1 txhdlcdat_7_1 txaisen_1 i ttl transmit sts-1 telecom bus ? channel 1 ? input data bus pin number 7: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 7: sts1txa_d7_1: this input pin along with ?sts1txa_d_1[6:0]? function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 1. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_1?. note: this input pin func tions as the msb (most significant bit) of the transmit (add) telecom bus, for channel 1. txhdlcdat_7_1 (transmit hdlc block data ? channel 1 ? input data pin 7) txaisen_1 (transmit ais enable ? channel 1) ae15 sts1txa_d0_2 txhdlcdat_0_2 txgfcmsb_2 i/o ttl/cmos transmit sts-1 telecom bus ? channel 2 ? input data bus pin number 0: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 0: this input pin along with ?sts1txa_d_2[7:1]? function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 2. this particular input pin functions as the lsb (least significant bit) input pi n on the transmit (add) telecom bus ? input data bus. the st s-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_2?. the lsb of any byte, which is being input into the ?sts-1 transmit telecom bus ? data bus (for channel 2) should be input via this pin. txhdlcdat_0_2 (transmit hdlc block data ? channel 2 ? input data pin 0) txgfcmsb_2 (transmit gfc msb indicator ? channel 2)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 67 ad15 sts1txa_d1_2 txhdlcdat_1_2 txgfc_2 i ttl transmit sts-1 telecom bus ? channel 2 ? input data bus pin number 1: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 1: this input pin along with ?sts1txa_d_2[7:2]? and ?sts1txa_d0_2 function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 2. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_2?. txhdlcdat_1_2 (transmit hdlc block data ? channel 2 ? input data pin 1) txgfc_2 (transmit gfc data ? channel 2) ac15 sts1txa_d2_2 txhdlcdat_2_2 txcelltxed_2 i/o ttl/cmos transmit sts-1 telecom bus ? channel 2 ? input data bus pin number 2: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 2: sts1txa_d2_2 this input pin along with ?sts1txa_d_2[7:3]? and ?sts1txa_d_2[1:0] function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 2. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_2?. txhdlcdat_2_2 (transmit hdlc block data ? channel 2 ? input data pin 2) txcelltxed_2 (cell transmitted ? channel 2) ag16 sts1txa_d3_2 txhdlcdat_3_2 ssi_neg i/o ttl/cmos transmit sts-1 telecom bus ? channel 2 ? input data bus pin number 3: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 3: sts1txa_d3_2: this input pin along with ?sts1txa_d_2[7:4]? and ?sts1txa_d_2[2:0] function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 2. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_2?. txhdlcdat_3_2 (transmit hdlc block data ? channel 2 ? input data pin 3) ssi_neg (slow speed interface data negative for ingress path)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 68 ag17 sts1txa_d4_2 txhdlcdat_4_2 txds3ohind_2 i/o ttl/cmos transmit sts-1 telecom bus ? channel 2 ? input data bus pin number 4: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 4: sts1txa_d4_2: this input pin along with ?sts1txa_d_2[7:5]? and ?sts1txa_d_2[3:0] function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 2. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_2?. txhdlcdat_4_2 (transmit hdlc block data ? channel 2 ? input data pin 4) txds3ohind_2 (transmit ds3 overhead indicator ? channel 2) af16 sts1txa_d5_2 txhdlcdat_5_2 txds3fp_2 i/o ttl/cmos transmit sts-1 telecom bus ? channel 2 ? input data bus pin number 5: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 5: sts1txa_d5_2: this input pin along with ?sts1txa_d_2[7:6]? and ?sts1txa_d_2[4:0] function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 2. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_2?. txhdlcdat_5_2 (transmit hdlc block data ? channel 2 ? input data pin 5) txds3fp_2 (transmit ds3 frame pulse ? channel 2) ag18 sts1txa_d6_2 txhdlcdat_6_2 txds3data_2 i ttl transmit sts-1 telecom bus ? channel 2 ? input data bus pin number 6: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 6: sts1txa_d6_2: this input pin along with ?sts1txa_d7_2? and ?sts1txa_d_2[5:0]? function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 2. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_2?. txhdlcdat_6_2 (transmit hdlc block data ? channel 2 ? input data pin 6) txds3data_2 (transmit ds3 data ? channel 2)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 69 ae16 sts1txa_d7_2 txhdlcdat_7_2 txaisen_2 i ttl transmit sts-1 telecom bus ? channel 2 ? input data bus pin number 7: the exact function of this pin depends upon whether the sts- 1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 transmit telecom bus ? input data bus pin number 7: sts1txa_d7_2: this input pin along with ?sts1txa_d_2[6:0]? function as the ?sts-1 transmit (add) telecom bus ? input data bus for channel 2. the sts-1 telecom bus interface will sample and latch this pin upon the falling edge of ?sts1txa_ck_2?. note: this input pin functions as the msb (most significant bit) of the transmit (add) telecom bus, for channel 2. if sts-1 telecom bus (channel 2) has not been enabled: if sts-1 telecom bus (channel 2) has not been enabled, then this particular pin can be configured to function in either of the following roles. txhdlcdat_7_2 (transmit hdlc block data ? channel 2 ? input data pin 7 ? high speed hdlc controller mode only) this input pin will function as a part of the ?transmit hdlc controller? byte-wide data input bus, whenever the user configures the ds3/e3 framer block (associated with channel 2) to operate in the ?high-spe ed hdlc controller? mode. this pin will function as data input pin # 2. txaisen_2 (transmit ais enable ? channel 2) this input pin permits the user to command the ds3/e3 frame generator block (associated with channel 2) to transmit the ds3/e3 ais indicator. pulling this input pin ?high? configures the ds3/e3 frame generator bl ock to generate and transmit the ds3/e3 ais indicator. pulling this input pin ?low? configures the ds3/e3 frame generator block to transmit normal ds3/e3 data-streams. note: the user should pull this pin to ?gnd? for normal operation r eceive s ystem s ide i nterface p ins
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 70 b15 c23 ag13 rxoh_0 rxoh_1 rxoh_2 o cmos receive overhead data output interface ? output this output pin functions as the ?receive overhead data? output for the receive system side interface when the xrt94l33 is configured to operat e in ds3/e3 mode, however, it functions as the ?recei ve sts-1 overhead data? output when the device is configured to operate in the sts-1 mode. when configured to operate in ds3/e3 mode: all overhead bits, which are received via the ?receive section? of the channel, will be output via this output pin, upon the rising edge of ?rxohclk_n?. when configured to operate in sts-1 mode: these output pins, along with ?rxohenable_n?, ?rxohclk_n? and ?rxohframe_n? function as the ?receive sts-1 toh and poh output port?. each bit, within the toh and poh bytes (within the incoming sts-1 data stream) is updated upon the falling edge of ?rxohclk_n?. as a consequence, external circuitry receiving this data, should sample this data upon the rising edge of ?rxohclk_n?. notes: 1. the external circuitry can de termine whether or not it is receiving poh or toh data via this output pin. the ?rxohenable_n? output pin will be ?high? anytime poh data is being output via these output pins. conversely, the ?rxohenable_n? output pi n will be ?low? anytime toh data is being output via these output pins. 2. toh and poh data, associated with receive sts-1 toh and poh processor block ? channel 0 will be output via the ?rxoh_0, and so on.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 71 c15 d21 af13 rxohenable_0 rxohenable_1 rxohenable_2 o cmos receive overhead data output interface ? enable output this output pin functions as the ?receive overhead enable? output for the receive system side interface when the xrt94l33 is configured to operat e in ds3/e3 mode, however, it functions as the ?recei ve sts-1 overhead data? output when the device is configured to operate in the sts-1 mode. when configured to operate in ds3/e3 mode: the channel will assert this ou tput signal for one ?rxohclk_n? period when it is safe for the local terminal equipment to sample the data on the ?r xoh_n? output pin. when configured to operate in sts-1 mode: these output pins, along with ?rxohclk_n?, ?rxohframe_n? and ?rxoh_n? function as the ?receive sts-1 toh and poh output port?. these output pins indicate whet her poh or toh data is being output via the ?rxoh_n? output pins. these output pins will toggle ?high? coincident with when poh data is being output via the ?rxoh_n? output pins. conversely, these output pins will toggle ?low? coincident with when toh data is being output vi a the ?rxoh_n? output pins. these output pins are upd ated upon the falling edge of ?rxohclk_n?. as a consequence, external circuitry, receiving this data, should sample this data upon the rising edge of ?rxohclk_n?. d15 e20 ae13 rxohclk_0 rxohclk_1 rxohclk_2 o cmos receive overhead data output interface ? clock this output pin functions as the ?receive overhead clock? output for the receive system side interface when the xrt94l33 is configured to operat e in ds3/e3 mode, however, it functions as the ?receive sts-1 overhead clock? output when the device is configured to operate in the sts-1 mode. when configured to operate in ds3/e3 mode: the channel will output the overhead bits (within the incoming ds3 or e3 frames) via the rxoh_n output pin, upon the falling edge of this clock signal. as a consequence, the user?s local terminal equipment should use the rising edge of this clock signal to sample the data on both the ?rxoh? and ?rxo hframe? output pins. note: this clock signal is always active. when configured to operate in sts-1 mode: these output pins, along with ?rxoh_n?, ?rxohframe_n?, and ?rxohenable_n? function as the ?receive sts-1 toh and poh output port?. these output pins function as the ?clock output? signals for the receive sts-1 toh and poh output port. the ?rxoh_n?, ?rxsts1frame_n? and ?rxohenable_n? output pins are updated upon the falling edge of this clock signal.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 72 e15 d22 ad13 rxohframe_0 rxohframe_1 rxohframe_2 o cmos receive overhead data interface ? framing pulse indicator this output pin functions as the ?receive overhead clock? output for the receive system side interface when the xrt94l33 is configured to operat e in ds3/e3 mode, however, it functions as the ?receive sts-1 overhead clock? output when the device is configured to operate in the sts-1 mode. when configured to operate in ds3/e3 mode: this output pin pulses ?high? whenever the receive overhead data output interface block outputs the first overhead bit of a new ds3 or e3 frame. when configured to operate in sts-1 mode: these output pins, along with ?rxoh_n?, ?rxohenable_n? and ?rxohclk_n? function as the ?receive sts-1 toh and poh output port?. these output pins will pulse ?high? coincident with either of the following events. when the very first toh byte (a1), of a given sts-1 frame, is being output via the correspo nding ?rxoh_n? output pin. when the very first poh byte (j1), of a given sts-1 frame, is being output via the correspo nding ?rxoh_n? output pin. the external circuitry can determine whether these output pins are pulsing high for the first toh or poh byte by checking the state of the corresponding ?rxohenable_n? output pin. y26 rxperr o cmos for mapper applications, pleas e let this pin ?float?. ab27 rxpeop o cmos for mapper applications, pleas e let this pin ?float?. aa26 rxpdval o cmos for mapper applications, pleas e let this pin ?float?. v24 rxmod_0 o cmos for mapper applications, pleas e let this pin ?float?. v25 rxuprty/ rxpprty o cmos for mapper applications, pleas e let this pin ?float?.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 73 u23 w26 u24 aa27 y27 u25 v26 w27 t23 t24 u26 t25 v27 t26 u27 t27 rxudata_0/ rxpdata_0 rxudata_1/ rxpdata_1 rxudata_2/ rxpdata_2 rxudata_3/ rxpdata_3 rxudata_4/ rxpdata_4 rxudata_5/ rxpdata_5 rxudata_6/ rxpdata_6 rxudata_7/ rxpdata_7 rxudata_8/ rxpdata_8 rxudata_9/ rxpdata_9 rxudata_10/ rxpdata_10 rxudata_11/ rxpdata_11 rxudata_12/ rxpdata_12 rxudata_13/ rxpdata_13 rxudata_14/ rxpdata_14 rxudata_15/ rxpdata_15 o cmos for mapper applications, please let these pins ?float?. r23 r24 r25 r26 r27 rxuaddr_0 rxuaddr_1 rxuaddr_2 rxuaddr_3 rxuaddr_4 i ttl for mapper applications, please connect these pins to gnd p27 rxuclav/ rxppa o cmos for mapper applications, pleas e let this pin ?float?. p25 rxusoc/ rxpsop/ rxpsoc o cmos for mapper applications, pleas e let this pin ?float?. p23 rxtsx/ rxpsof o cmos for mapper applications, pleas e let this pin ?float?. p24 rxuenb_l/ rxpenb_l i ttl for mapper applications, please connect this pin to vdd p26 rxuclko/ rxpclko o cmos for mapper applications, pleas e let this pin ?float?.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 74 n27 rxuclk/ rxpclk i ttl for mapper applications, please connect this pin to gnd a16 j23 ac13 extlos_0 extlos_1 extlos_2 i ttl receive los (loss of signal) indicator input (from the xrt94l33 ds3/e3/sts-1 liu ic): this input pin, is intended to be connected to each of the rlos (receive loss of signal) output pins of the xrt94l33 ds3/e3/sts-1 liu ic. the user can monitor the state of this input pin by reading the state of bit 0 (rlos) within the line interface scan register (address = 0xxx, 0xxx). if this input pin is ?low?, then it means that the corresponding channel (within the xrt94l33) is currently not declaring an los condition. however, if this input pin is ?high?, then it means that this particular channel is currently declaring an los condition. note: asserting this input pin will cause the xrt94l33 framer/uni ic to declare an ?los (loss of signal) condition. therefore, this input pin should not be used as a general purpose input pin. a14 d20 ae14 rxoof_0 rxoof_1 rxoof_2 o cmos receive sts-1/ds3/e3 out of frame indicator the sts-1/ds3/e3 receive ds3 fr amer will assert this output signal whenever it has declar ed an ?out of frame? (oof) condition with the incoming ds3 frames. this signal is negated when the framer correctly locates the f- and m-bits and regains synchronization with the ds3 frame. a15 b24 ag14 rxlos_0 rxlos_1 rxlos_2 o cmos sts-1/ds3/e3 framer - loss of signal output indicator: this pin is asserted when the receive section of the channel encounters 180 consecutive 0?s (f or ds3 applications) or 32 consecutive 0?s (for e3 appli cations) via the rxpos_n and rxneg pins. for sts-1 applications, users can set the los threshold value in the receive los threshold register. (rxstoh_los_th, address location: 0xn02e ? 0xn02f) this pin will be negated once the receive ds3/e3 framer has detected at least 60 ?1s? out of 180 consecutive bits (for ds3 applications) or has detected at least four consecutive 32 bit strings of data that cont ain at least 8 ?1s? in the receive path.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 75 sts-1 t elecom b us i nterface ? r eceive d irection a21 sts1rxd_ck_0 rxvalidfcs_0 rxgfcclk_0 o cmos receive sts-1/sts-3 telecom bus clock output ? channel 0; the exact function of this input pin depends upon whether the ?sts-1 telecom bus interface associated with channel 0? is enabled or not, as described below. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 receive telecom bus clock output ? channel 0; sts1rxd_ck_0: all signals, which are output via the ?receive telecom bus ? channel 0? are clocked out upon the rising edge of this clock signal. this includes the following signals. ? sts1rxd_d_0[7:0] ? sts1rxd_alarm_0 ? sts1rxd_dp_0 ? sts1rxd_pl_0 ? sts1rxd_c1j1_0 this clock signal will operat e at 19.44mhz (for sts-3 mode) or 6.48mhz (fro sts-1 mode) rxvalidfcs_0 (receive hdlc block valid fcs indicator ? channel 0) rxgfcclk_0 (receive atm gfc clock signal ? channel 0)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 76 h24 sts1rxd_ck_1 rxvalidfcs_1 rxgfcclk_1 txp_stpa o cmos receive sts-1 telecom bus clock output ? channel 1; the exact function of this input pin depends upon whether the ?sts-1 telecom bus interface associated with channel 1? is enabled or not, as described below. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 receive telecom bus clock output ? channel 1; sts1rxd_ck_1: all signals, which are output via the ?receive telecom bus ? channel 1? are clocked out upon the rising edge of this clock signal. this includes the following signals. ? sts1rxd_d_1[7:0] ? sts1rxd_alarm_1 ? sts1rxd_dp_1 ? sts1rxd_pl_1 ? sts1rxd_c1j1_1 this clock signal will operate at 19.44mhz. (for sts-3 mode) or 6.48mhz (fro sts-1 mode) rxvalidfcs_1 (receive hdlc block valid fcs indicator ? channel 1) rxgfcclk_1 (receive atm gfc clock signal ? channel 1) txp_stpa (transmit ppp level 2 selected channel packet available) ag8 sts1rxd_ck_2 rxvalidfcs_2 rxgfcclk_2 o cmos receive sts-1 telecom bus clock output ? channel 2; the exact function of this input pin depends upon whether the ?sts-1 telecom bus interface associated with channel 2? is enabled or not, as described below. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 receive telecom bus clock output ? channel 2; sts1rxd_ck_2: all signals, which are output via the ?receive telecom bus ? channel 2? are clocked out upon the rising edge of this clock signal. this includes the following signals. ? sts1rxd_d_2[7:0] ? sts1rxd_alarm_2 ? sts1rxd_dp_2 ? sts1rxd_pl_2 ? sts1rxd_c1j1_2 this clock signal will operate at 19.44mhz. (for sts-3 mode) or 6.48mhz (fro sts-1 mode) rxvalidfcs_2 (receive hdlc block valid fcs indicator ? channel 2) rxgfcclk_2 (receive atm gfc clock signal ? channel 2)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 77 a20 sts1rxd_pl_0 rxidle_0 rxlcd_0 o cmos sts-1 receive (drop) telecom bus ? payload indicator output signal ? channel 0: the exact function of this output pin depends upon whether the user has enabled or disabled the ?sts-1 telecom bus interface block? associated with channel 0. if the sts-1 telecom bus interface (associated with channel 0) is enabled ? sts-1/sts-1 receive (drop) telecom bus ? payload indicator output ? sts1rxd_pl_0: this output pin indicates whether or not transport overhead bytes are being output via the ?sts1rxd_d_0[7:0]? output pins. this output pin is pulled ?low? for the duration that the sts-1 receive telecom bus is transmitting a transport overhead byte via the ?sts1rxd_d_0[7:0]? output pins. conversely, this output pin is pulled ?high? for the duration that the sts-1 receive telecom bus is transmitting something other than a transport overhead byte via the ?sts1rxd_d_0[7:0]? output pins. rxidle_0 (receive hdlc block idle indicator ? channel 0) rxlcd_0 (receive cell processor loss of cell delineation ? channel 0) d26 sts1rxd_pl_1 rxidle_1 rxlcd_1 o cmos sts-1 receive (drop) telecom bus ? payload indicator output signal ? channel 1: the exact function of this output pin depends upon whether the user has enabled or disabled the ?sts-1 telecom bus interface block? associated with channel 1. if the sts-1 telecom bus interface (associated with channel 1) is enabled ? sts-1/sts-1 receive (drop) telecom bus ? payload indicator output ? sts1rxd_pl_1: this output pin indicates whether or not transport overhead bytes are being output via the ?sts1rxd_d_1[7:0]? output pins. this output pin is pulled ?low? for the duration that the sts-1 receive telecom bus is transmitting a transport overhead byte via the ?sts1rxd_d_1[7:0]? output pins. conversely, this output pin is pulled ?high? for the duration that the sts-1 receive telecom bus is transmitting something other than a transport overhead byte via the ?sts1rxd_d_1[7:0]? output pins. rxidle_1 (receive hdlc block idle indicator ? channel 1) rxlcd_1 (receive cell processor loss of cell delineation ? channel 1)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 78 ae11 sts1rxd_pl_2 rxidle_2 rxlcd_2 o cmos sts-1 receive (drop) telecom bus ? payload indicator output signal ? channel 2: the exact function of this output pin depends upon whether the user has enabled or disabled the ?sts-1 telecom bus interface block? associated with channel 2. if the sts-1 telecom bus interface (associated with channel 2) is enabled ? sts-1/sts-1 receive (drop) telecom bus ? payload indicator output ? sts1rxd_pl_2: this output pin indicates whether or not transport overhead bytes are being output via the ?sts1rxd_d_2[7:0]? output pins. this output pin is pulled ?low? for the duration that the sts-1 receive telecom bus is transmitting a transport overhead byte via the ?sts1rxd_d_2[7:0]? output pins. conversely, this output pin is pulled ?high? for the duration that the sts-1 receive telecom bus is transmitting something other than a transport overhead byte via the ?sts1rxd_d_2[7:0]? output pins. rxidle_2 (receive hdlc block idle indicator ? channel 2) rxlcd_2 (receive cell processor loss of cell delineation ? channel 2)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 79 c17 sts1rxd_c1j1_0 txds3lineclk_0 o cmos sts-1 receive telecom bus - c1/j1 byte phase indicator output signal ? channel 0: the exact function of this output pin depends upon whether the sts-1 telecom bus interface for channel 0 has been enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 receive telecom bus ? c1/j1 byte phase indicator output signal: this output pin pulses ?high? under the following two conditions. whenever the c1 byte is being output via the ?sts1rxd_d_0[7:0]? output, and whenever the j1 byte is being output via the ?sts1rxd_d_0[7:0]? output. notes: 1. the sts-1 receive (drop) telecom bus (associated with channel 0) will indicate that it is transmitting the c1 byte (via the sts1rxd_d_0[7:0] out put pins), by pulsing this output pin ?high? (for one period of ?sts1rxd_ck_0?) and keeping the ?sts1rxd_pl_0? output pin pulled ?low. 2. the sts-1 receive (drop) telecom bus (associated with channel 0) will indicate that it is transmitting the j1 byte (via the sts1rxd_d_0[7:0] out put pins), by pulsing this output pin ?high? (for one period of ?sts1rxd_ck_0?) while the ?sts1txd_pl_0? output pin is pulled ?high?. txds3lineclk_0 (transmit ds3/e3/sts-1 line clock to liu ? channel 0)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 80 e25 sts1rxd_c1j1_1 txds3lineclk_1 o cmos sts-1 receive telecom bus - c1/j1 byte phase indicator output signal ? channel 1: the exact function of this output pin depends upon whether the sts-1 telecom bus interface for channel 1 has been enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 receive telecom bus ? c1/j1 byte phase indicator output signal: this output pin pulses ?high? under the following two conditions. whenever the c1 byte is being output via the ?sts1rxd_d_1[7:0]? output, and whenever the j1 byte is being output via the ?sts1rxd_d_1[7:0]? output. notes: 1. the sts-1 receive (drop) telecom bus (associated with channel 1) will indicate that it is transmitting the c1 byte (via the sts1rxd_d_1[7:0] out put pins), by pulsing this output pin ?high? (for one period of ?sts1rxd_ck_1?) and keeping the ?sts1rxd_pl_1? output pin pulled ?low. 2. the sts-1 receive (drop) telecom bus (associated with channel 1) will indicate that it is transmitting the j1 byte (via the sts1rxd_d_1[7:0] out put pins), by pulsing this output pin ?high? (for one period of ?sts1rxd_ck_1?) while the ?sts1txd_pl_1? output pin is pulled ?high?. txds3lineclk_1 (transmit ds3/e3/sts-1 line clock to liu ? channel 1)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 81 af10 sts1rxd_c1j1_2 txds3lineclk_2 o cmos sts-1 receive telecom bus - c1/j1 byte phase indicator output signal ? channel 2: the exact function of this output pin depends upon whether the sts-1 telecom bus interface for channel 2 has been enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 receive telecom bus ? c1/j1 byte phase indicator output signal: this output pin pulses ?high? under the following two conditions. whenever the c1 byte is being output via the ?sts1rxd_d_2[7:0]? output, and whenever the j1 byte is being output via the ?sts1rxd_d_2[7:0]? output. notes: 1. the sts-1 receive (drop) telecom bus (associated with channel 2) will indicate that it is transmitting the c1 byte (via the sts1rxd_d_2[7:0] out put pins), by pulsing this output pin ?high? (for one period of ?sts1rxd_ck_2?) and keeping the ?sts1rxd_pl_2? output pin pulled ?low. 2. the sts-1 receive (drop) telecom bus (associated with channel 2) will indicate that it is transmitting the j1 byte (via the sts1rxd_d_2[7:0] out put pins), by pulsing this output pin ?high? (for one period of ?sts1rxd_ck_2?) while the ?sts1txd_pl_2? output pin is pulled ?high?. txds3lineclk_2 (transmit ds3/e3/sts-1 line clock to liu ? channel 2)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 82 b18 sts1rxd_dp_0 txds3pos_0 o cmos sts-1 receive (drop) telecom bus ? parity output pin ? channel 0: the exact function of this output pin depends upon whether the sts-1 telecom bus interface for channel 0 has been enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 receive telecom bus ? parity output pin: this output pin can be configur ed to function as one of the following. the even or odd parity value of the bits which are output via the ?sts1rxd_d_0[7:0]? output pins. the even or odd parity value of the bits which are being output via the ?sts1rxd_d_0[7:0]? output pins and the states of the ?sts1rxd_pl_0? and ?sts1rxd_c1j1_0? output pins. this output pin will ultimately be used (by ?drop-side? circuitry) to verify the verify of the data which is output via the ?sts-1 telecom bus interface associated with channel 0. note: the user can make any one of these configuration selections by writing the appropriate value into the ?telecom bus control? register (address location = 0x013b). txds3pos_0 (transmit ds3/e3/sts-1 line data positive to liu? channel 0) g24 sts1rxd_dp_1 txds3pos_1 o cmos sts-1 receive (drop) telecom bus ? parity output pin ? channel 1: the exact function of this output pin depends upon whether the sts-1 telecom bus interface for channel 1 has been enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 receive telecom bus ? parity output pin: this output pin can be configur ed to function as one of the following. the even or odd parity value of the bits output via the ?sts1rxd_d_1[7:0]? output pins. the even or odd parity value of the bits being output via the ?sts1rxd_d_1[7:0]? output pins and the states of the ?sts1rxd_pl_1? and ?sts1rxd_c1j1_1? output pins. this output pin will ultimately be used (by ?drop-side? circuitry) to verify of the data which is output via the ?sts-1 telecom bus interface associated with channel 1. note: the user can make any one of these configuration selections by writing the appropriate value into the ?telecom bus control? register (address location = 0x013a). txds3pos_1 (transmit ds3/e3/sts-1 line data positive to liu? channel 1)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 83 ag9 sts1rxd_dp_2 txds3pos_2 o cmos sts-1 receive (drop) telecom bus ? parity output pin ? channel 2: the exact function of this output pin depends upon whether the sts-1 telecom bus interface for channel 2 has been enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 receive telecom bus ? parity output pin: this output pin can be configur ed to function as one of the following. the even or odd parity value of the bits output via the ?sts1rxd_d_2[7:0]? output pins. the even or odd parity value of the bits being output via the ?sts1rxd_d_2[7:0]? output pins and the states of the ?sts1rxd_pl_2? and ?sts1rxd_c1j1_2? output pins. this output pin will ultimately be used (by ?drop-side? circuitry) to verify the verify of the data which is output via the ?sts-1 telecom bus interface associated with channel 2. note: the user can make any o ne of these configuration selections by writing the appropriate value into the ?telecom bus control? register (address location = 0x0139). txds3pos_2 (transmit ds3/e3/sts-1 line data positive to liu? channel 2) a19 sts1rxd_alarm_0 txds3neg_0/ o cmos sts-1 receive (drop) telecom bus ? alarm indicator output signal ? channel 0: the exact function of this output pin depends upon whether the sts-1 telecom bus interface for channel 0 has been enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 receive telecom bus ? al arm indicator output signal: this output pin pulses ?high?, coincident with any sts-1 signal (that is being output via the ?sts1rxd_d_0[7:0]? output pins) that is carrying an ais-p indicator. this output pin is ?low? for all other conditions. txds3neg_0 (transmit ds3/e3 line data negative to liu ? channel 0)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 84 h23 sts1rxd_alarm_1 txds3neg_1/ o cmos sts-1 receive (drop) telecom bus ? alarm indicator output signal ? channel 1: the exact function of this output pin depends upon whether the sts-1 telecom bus interface for channel 1 has been enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 receive telecom bus ? al arm indicator output signal: this output pin pulses ?high?, coincident with any sts-1 signal (that is being output via the ?sts1rxd_d_1[7:0]? output pins) that is carrying an ais-p indicator. this output pin is ?low? for all other conditions. txds3neg_1 (transmit ds3/e3 line data negative to liu ? channel 1) ab12 sts1rxd_alarm_2 txds3neg_2/ o cmos sts-1 receive (drop) telecom bus ? alarm indicator output signal ? channel 2: the exact function of this output pin depends upon whether the sts-1 telecom bus interface for channel 2 has been enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 receive telecom bus ? al arm indicator output signal: this output pin pulses ?high?, coincident with any sts-1 signal (that is being output via the ?sts1rxd_d_2[7:0]? output pins) that is carrying an ais-p indicator. this output pin is ?low? for all other conditions. txds3neg_2 (transmit ds3/e3 line data negative to liu ? channel 2) f16 sts1rxd_d0_0 rxhdlcdat_0_0 rxgfcmsb_0 o cmos receive sts-1 telecom bus ? channel 0 ? output data bus pin number 0: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 0: sts1rxd_d0_0 this output pin along with ?sts1rxd_d_0[7:1]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 0. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_0:. note: this input pin functions as the lsb (least significant bit) of the receive (drop) telecom bus for channel 0. rxhdlcdat_0_0 (receive hdlc block data output ? channel 0 ? output data bus pin 0) rxgfcmsb_0 (receive gfc msb indicator ? channel 0)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 85 e16 sts1rxd_d1_0 rxhdlcdat_1_0 rxgfc_0 o cmos receive sts-1 telecom bus ? channel 0 ? output data bus pin number 1: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 1: sts1rxd_d1_0 this output pin along with ?sts1rxd_d_0[7:2]? and ?sts1rxd_d0_0 function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 0. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_0:. rxhdlcdat_1_0 (receive hdlc block data output ? channel 0 ? output data bus pin 1): rxgfc_0 (receive gfc output data ? channel 0) d16 sts1rxd_d2_0 rxhdlcdat_2_0 rxcellrxed_0 o cmos receive sts-1 telecom bus ? channel 0 ? output data bus pin number 2: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 2: sts1rxd_d2_0 this output pin along wi th ?sts1rxd_d_0[7:3]? and ?sts1rxd_d_0[1:0]? functi on as the ?sts-3/stm-1 receive (drop) telecom bus ? output data bus for channel 0. the sts-3/stm-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_0:. rxhdlcdat_2_0 (receive hdlc block data output ? channel 0 ? output data bus pin 2) rxcellrxed_0 (receive cell received indicator ? channel 0)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 86 b17 sts1rxd_d3_0 rxhdlcdat_3_0 sse_clk o o io o cmos cmos ttl/cmos cmos receive sts-1 telecom bus ? channel 0 ? output data bus pin number 3: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 3: sts1rxd_d3_0 this output pin along with ?sts1rxd_d_0[7:4]? and ?sts1rxd_d_0[2:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 0. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_0:. rxhdlcdat_3_0 (receive hdlc block data output ? channel 0 ? output data bus pin 3) sse_clk (slow speed clock interface for egress path) c16 sts1rxd_d4_0 rxhdlcdat_4_0 rxohind_0 o cmos receive sts-1 telecom bus ? channel 0 ? output data bus pin number 4: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 4: sts1rxd_d4_0 this output pin along with ?sts1rxd_d_0[7:5]? and ?sts1rxd_d_0[3:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 0. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_0:. rxhdlcdat_4_0 (receive hdlc block data output ? channel 0 ? output data bus pin 4) rxohind_0 (receive overhead indicator ? channel 0) a18 sts1rxd_d5_0 rxhdlcdat_5_0 rxds3fp_0 o cmos receive sts-1 telecom bus ? channel 0 ? output data bus pin number 5: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 5: sts1rxd_d5_0 this output pin along with ?sts1rxd_d_0[7:6]? and ?sts1rxd_d_0[4:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 0. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_0:. rxhdlcdat_5_0 (receive hdlc block data output ? channel 0 ? output data bus pin 5) rxds3fp_0 (receive ds3 frame pulse ? channel 0)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 87 b16 sts1rxd_d6_0 rxhdlcdat_6_0 rxds3data_0 o cmos receive sts-1 telecom bus ? channel 0 ? output data bus pin number 6: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 6: sts1rxd_d6_0 this output pin along with ?sts1rxd_d7_0? and ?sts1rxd_d_0[5:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 0. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_0:. rxhdlcdat_6_0 (receive hdlc block data output ? channel 0 ? output data bus pin 6) rxds3data_0 (receive ds3 data ? channel 0) a17 sts1rxd_d7_0 rxhdlcdat_7_0 rxds3clk_0 o cmos receive sts-1 telecom bus ? channel 0 ? output data bus pin number 7: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 0 is enabled or not. if sts-1 telecom bus (channel 0) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 7: sts1rxd_d7_0 this output pin along with ?sts1rxd_d_0[6:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 0. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_0:. note: this output pin functions as the msb (most significant bit) for the sts-1 receive (drop) telecom bus interface ? output data bus (channel 0). rxhdlcdat_7_0 (receive hdlc block data output ? channel 0 ? output data bus pin 7) rxds3clk_0 (receive ds3 clock ? channel 0)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 88 f24 sts1rxd_d0_1 rxhdlcdat_0_1 rxgfcmsb_1 o cmos receive sts-1 telecom bus ? channel 1 ? output data bus pin number 0 : the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 0: sts1rxd_d0_1 this output pin along with ?sts1rxd_d_1[7:1]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 1. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_1. note: this input pin functions as the lsb (least significant bit) of the re ceive (drop) telecom bus for channel 1. rxhdlcdat_0_1 (receive hdlc block data output ? channel 1 ? output data bus pin 0) rxgfcmsb_1 (receive gfc msb indicator ? channel 1) h22 sts1rxd_d1_1 rxhdlcdat_1_1 rxgfc_1 o cmos receive sts-1 telecom bus ? channel 1 ? output data bus pin number 1: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 1: sts1rxd_d1_1 this output pin along with ?sts1rxd_d_1[7:2]? and ?sts1rxd_d0_1 function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 1. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_1. rxhdlcdat_1_1 (receive hdlc block data output ? channel 1 ? output data bus pin 1) rxgfc_1 (receive gfc output data ? channel 1)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 89 d25 sts1rxd_d2_1 rxhdlcdat_2_1 rxcellrxed_1 o cmos receive sts-1 telecom bus ? channel 1 ? output data bus pin number 2: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 2: sts1rxd_d2_1 this output pin along with ?sts1rxd_d_1[7:3]? and ?sts1rxd_d_1[1:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 1. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_1. rxhdlcdat_2_1 (receive hdlc block data output ? channel 1 ? output data bus pin 2) rxcellrxed_1 (receive cell received indicator ? channel 1) g23 sts1rxd_d3_1 rxhdlcdat_3_1 sse_pos o o io o cmos cmos ttl/cmos cmos receive sts-1 telecom bus ? channel 1 ? output data bus pin number 3: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 3: sts1rxd_d3_1 this output pin along with ?sts1rxd_d_1[7:4]? and ?sts1rxd_d_1[2:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 1. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_1. rxhdlcdat_3_1 (receive hdlc block data output ? channel 1 ? output data bus pin 3) sse_pos (slow speed interface data positive for egress path)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 90 d23 sts1rxd_d4_1 rxhdlcdat_4_1 rxohind_1 o cmos receive sts-1 telecom bus ? channel 1 ? output data bus pin number 4: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 4: sts1rxd_d4_1 this output pin along with ?sts1rxd_d_1[7:5]? and ?sts1rxd_d_1[3:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 1. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_1. rxhdlcdat_4_1 (receive hdlc block data output ? channel 1 ? output data bus pin 4) rxohind_1 (receive overhead indicator ? channel 1) e21 sts1rxd_d5_1 rxhdlcdat_5_1 rxds3fp_1 o cmos receive sts-1 telecom bus ? channel 1 ? output data bus pin number 5: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 5: sts1rxd_d5_1 this output pin along with ?sts1rxd_d_1[7:6]? and ?sts1rxd_d_1[4:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 1. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_1. rxhdlcdat_5_1 (receive hdlc block data output ? channel 1 ? output data bus pin 5) rxds3fp_1 (receive ds3 frame pulse ? channel 1) c24 sts1rxd_d6_1 rxhdlcdat_6_1 rxds3data_1 o cmos receive sts-1 telecom bus ? channel 1 ? output data bus pin number 6: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 6: sts1rxd_d6_1 this output pin along with ?sts1rxd_d7_1? and ?sts1rxd_d_1[5:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 1. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_1. rxhdlcdat_6_1 (receive hdlc block data output ? channel 1 ? output data bus pin 6): rxds3data_1 (receive ds3 data ? channel 1):
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 91 f20 sts1rxd_d7_1 rxhdlcdat_7_1 rxds3clk_1 o cmos receive sts-1 telecom bus ? channel 1 ? output data bus pin number 7: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 1 is enabled or not. if sts-1 telecom bus (channel 1) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 7: sts1rxd_d7_1 this output pin along with ?sts1rxd_d_1[6:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 1. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_1. note: this output pin functions as the msb (most significant bit) for the sts-1 receive (drop) telecom bus interface ? output data bus (channel 1). rxhdlcdat_7_1 (receive hdlc block data output ? channel 1 ? output data bus pin 7) rxds3clk_1 (receive ds3 clock ? channel 1) ac12 sts1rxd_d0_2 rxhdlcdat_0_2 rxgfcmsb_2 o cmos receive sts-1 telecom bus ? channel 2 ? output data bus pin number 0: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 0: sts1rxd_d0_2 this output pin along with ?sts1rxd_d_2[7:1]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 2. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_2. note: this input pin functions as the lsb (least significant bit) of the re ceive (drop) telecom bus for channel 2. rxhdlcdat_0_2 (receive hdlc block data output ? channel 2 ? output data bus pin 0) rxgfcmsb_2 (receive gfc msb indicator ? channel 2)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 92 ad12 sts1rxd_d1_2 rxhdlcdat_1_2 rxgfc_2 o cmos receive sts-1 telecom bus ? channel 2 ? output data bus pin number 1: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 1: sts1rxd_d1_2 this output pin along with ?sts1rxd_d_2[7:2]? and ?sts1rxd_d0_2 function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 2. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_2. rxhdlcdat_1_2 (receive hdlc block data output ? channel 2 ? output data bus pin 1) rxgfc_2 (receive gfc output data ? channel 2) af11 sts1rxd_d2_2 rxhdlcdat_2_2 rxcellrxed_2 o cmos receive sts-1 telecom bus ? channel 2 ? output data bus pin number 2: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 2: sts1rxd_d2_2 this output pin along with ?sts1rxd_d_2[7:3]? and ?sts1rxd_d_2[1:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 2. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_2. rxhdlcdat_2_2 (receive hdlc block data output ? channel 2 ? output data bus pin 2) rxcellrxed_2 (receive cell received indicator ? channel 2)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 93 ae12 sts1rxd_d3_2 rxhdlcdat_3_2 sse_neg o o io o cmos cmos ttl/cmos cmos receive sts-1 telecom bus ? channel 2 ? output data bus pin number 3: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 3: sts1rxd_d3_2 this output pin along with ?sts1rxd_d_2[7:4]? and ?sts1rxd_d_2[2:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 2. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_2. rxhdlcdat_3_2 (receive hdlc block data output ? channel 2 ? output data bus pin 3) sse_neg (slow speed interface data negative for egress path) ag10 sts1rxd_d4_2 rxhdlcdat_4_2 rxohind_2 o cmos receive sts-1 telecom bus ? channel 2 ? output data bus pin number 4: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 4: sts1rxd_d4_2 this output pin along with ?sts1rxd_d_2[7:5]? and ?sts1rxd_d_2[3:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 2. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_2. rxhdlcdat_4_2 (receive hdlc block data output ? channel 2 ? output data bus pin 4) rxohind_2 (receive overhead indicator ? channel 2)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 94 af12 sts1rxd_d5_2 rxhdlcdat_5_2 rxds3fp_2 o cmos receive sts-1 telecom bus ? channel 2 ? output data bus pin number 5: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 5: sts1rxd_d5_2 this output pin along with ?sts1rxd_d_2[7:6]? and ?sts1rxd_d_2[4:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 2. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_2. rxhdlcdat_5_2 (receive hdlc block data output ? channel 2 ? output data bus pin5): this output pin along with rxhdlcdat_ rxds3fp_2 (receive ds3 frame pulse ? channel 2) ag11 sts1rxd_d6_2 rxhdlcdat_6_2 rxds3data_2 o cmos receive sts-1 telecom bus ? channel 2 ? output data bus pin number 6: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 6: sts1rxd_d6_2 this output pin along with ?sts1rxd_d7_2? and ?sts1rxd_d_2[5:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 2. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_2. rxhdlcdat_6_2 (receive hdlc block data output ? channel 2 ? output data bus pin 6) rxds3data_2 (receive ds3 data ? channel 2)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 95 ag12 sts1rxd_d7_2 rxhdlcdat_7_2 rxds3clk_2 o cmos receive sts-1 telecom bus ? channel 2 ? output data bus pin number 7: the exact function of this output pin depends upon whether the sts-1 telecom bus interface, associated with channel 2 is enabled or not. if sts-1 telecom bus (channel 2) has been enabled ? sts-1 receive telecom bus ? output data bus pin number 7: sts1rxd_d7_2 this output pin along with ?sts1rxd_d_2[6:0]? function as the ?sts-1 receive (drop) telecom bus ? output data bus for channel 2. the sts-1 telecom bus interface will update the data via this output upon the rising edge of ?sts1rxd_ck_2. note: this output pin functions as the msb (most significant bit) for the sts-1 receive (drop) telecom bus interface ? output data bus (channel 2). rxhdlcdat_7_2 (receive hdlc block data output ? channel 2 ? output data bus pin 7) rxds3clk_2 (receive ds3 clock ? channel 2)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 96 r eceive t ransport o verhead i nterface ad5 rxtohclk o cmos receive toh output port ? clock output: this output pin, along with ?rxtoh, rxtohvalid and ?rxtohframe? function as the ?receive toh output port?. the receive toh output port permi ts the user to obtain the value of the toh bytes, within the incoming sts-3/stm-1 signal. this output pin provides the user with a clock signal. if the ?rxtohvalid? output pin is ?high?, then the content s of the ?toh? bytes, within the incoming sts-3 data-stream will be serially output via the ?rxtoh? output. this data will be updated upon the falling edge of this clock signal. therefore, the user is advised to sample the data (at the ?rxtoh? output pin) upon the rising ed ge of this clock output signal. ac7 rxtohvalid o cmos receive toh output port ? toh valid (or ready) indicator: this output pin, along with ?rxtoh? and ?rxtohframe? function as the ?receive toh output port?. this output pin will toggle ?high? whenever valid ?toh? data is being output via the ?rxtoh? output pin. ae4 rxtoh o cmos receive toh output port ? output pin: this output pin, along with ?rxtohclk?, rxtohvalid? and ?rxtohframe? function as the ?receive toh output port. all toh data that resides within the incoming sts-3 data-stream will be output via this output pin. the ?rxtohvalid? output pin will toggle high, coincident with anytime a bit (from the receive sts-3 toh data) is being output via this output pin. the ?rxtohframe? output pin will pu lse ?high? (for eight periods of ?rxtohclk?) coincident to when the a1 byte is being output via this output pin. data, on this output pin, is updated upon the falling edge of ?rxtohclk?. ab8 rxtohframe o cmos receive toh output port ? sts-3/stm-1 frame indicator: this output pin, along with t he ?rxtohclk?, ?rxtohvalid? and ?rxtoh? output pins function as the ?receive toh output port?. this output pin will pulse ?high?, for one period of ?rxtohclk?, one ?rxtohclk? period prior to the very first ?toh? bit (of a given sts- 3 frame) being output via the ?rxtoh? output pin.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 97 ad7 rxldccval o cmos receive ? line dcc output port ? dcc value indicator output pin: this output pin, along with the ?rxtohclk? and the ?rxldcc? output pins function as the ?recei ve line dcc? output port of the xrt94l33. this output pin pulses ?high? coincident to when the ?receive line dcc? output port outputs a dcc bit via the ?rxldcc? output pin. this output pin is updated upon t he falling edge of ?rxtohclk?. the line dcc hdlc controller circuitry that is interfaced to this output pin, the ?rxldcc? and t he ?rxtohclk? pins is suppose to do the following. it should continuously sample and m onitor the state of this output pin upon the rising edge of ?rxtohclk?. anytime the ?line dcc hdlc? circuitry samples this output pin being ?high?, it should sample and latch the data on the ?rxldcc? output pin (as a valid line dcc bit) into the ?line dcc hdlc? circuitry. ae5 rxldcc o cmos receive ? line dcc output port ? output pin: this output pin, along with ?rxldccval? and the ?rxtohclk? output pins function as the ?recei ve line dcc? output port of the xrt94l33. this pin outputs the contents of the line dcc (e.g., the d4, d5, d6, d7, d8, d9, d10, d11 and d12 bytes), within the incoming sts-3 data-stream. the receive line dcc output port will assert the ?rxldccval? output pin, in order to indicate that the data, residing on the ?rxldcc? output pin is a valid line dcc byte. the receive line dcc output port will update the ?rxldccval? and the ?rxldcc? output pins upon the falling edge of the ?rxtohclk? output pin. the line dcc hdlc circuitry that is interfaced to this output pin, the ?rxldccval? and the ?rxtohclk? pins is suppose to do the following. it should continuously sample and monitor the state of the ?rxldccval? output pin upon the rising edge of ?rxtohclk?. anytime the ?line dcc hdlc? circuitry samples the ?rxldccval? output pin ?high?, it should sample and latch the contents of this output pin (as a valid line dcc bit) into the ?line dcc hdlc? circuitry. ad8 rxe1f1e2fp o cmos receive ? order-wire output port ? frame boundary indicator: this output pin, along with ?r xe1f1e2?, ?rxe1f1e2val? and the ?rxtohclk? output pins function as the ?receive order-wire output port of the xrt94l33. this output pin pulses ?high? (for one period of ?rxtohclk?) coincident to when the very first bit (of the e1 byte) is being output vi the ?rxe1f1e2? output pin.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 98 ac9 rxe1f1e2 o cmos receive ? order-wire output port ? output pin: this output pin, along with ?rxe 1f1e2val?, ?rxe1f1f2fp, and the ?rxtohclk? output pins function as the ?receive order-wire output port of the xrt94l33. this pin outputs the contents of th e ?order-wire? bytes (e.g., the e1, f1 and e2 bytes) within the incoming sts-3 data-stream. the receive order-wire output port will pulse the ?rxe1f1e2fp? output pin ?high? (for one period of ?rxtohclk?) coincident to when the very first bit (of the e1 byte) is being output via the ?rxe1f1e2? output pin. additionally, the re ceive order-wire output port will also assert the ?rxe1f1e2val? output pin, in order to indicate that the data, residing on the ?rxe1f1e2? output pin is valid ?order- wire? byte. the receive order-wire output port will update the ?rxe1f1e2val?, the ?rxe1f1e2f p? and the ?rxe1f1e2? output pins upon the falling edge of the ?rxtohclk? output pin. the ?receive order-wire? circuitry that is interfaced to this output pin, and the ?rxe1f1e2val?, t he ?rxe1f1e2? and the ?rxtohclk? pins is suppose to do the following. it should continuously sample and monitor the state of the ?rxe1f1e2val? and ?rxe1f1e2fp? output pins upon the rising edge of ?rxtohclk?. anytime the ?order-wire? circuitry samples the ?rxe1f1e2val? and ?rxe1f1e2fp output pins ?high, it should begin to sample and latch the contents of this output pin (as a valid ?order-wire? bit) into the ?order-wire? circuitry. the ?order-wire? circuitry should continue to sample and latch the contents of the output pin until the ?rxe1f2e2val? output pin is sampled ?low?. ac8 rxsdcc o cmos receive ? section dcc output port ? output pin: this output pin, along with ?rxsdccval? and the ?rxtohclk? output pins function as the ?recei ve section dcc? output port of the xrt94l33. this pin outputs the c ontents of the section dcc (e.g., the d1, d2 and d3 bytes), within the incoming sts-3 data-stream. the receive section dcc output port will assert the ?rxsdccval? output pin, in order to indicate that the data, residing on the ?rxsdcc? output pin is a valid section dcc byte. the receive section dcc output port will update the ?rxsdccval? and the ?rxsdcc? output pins upon the falling edge of the ?rxtohclk? output pin. the section dcc hdlc circuitry that is interfaced to this output pin, the ?rxsdccval? and the ?rxtohclk? pins is suppose to do the following. it should continuously sample and monitor the state of the ?rxsdccval? output pin upon the rising edge of ?rxtohclk?. anytime the ?section dcc hdlc? circuitry samples the ?rxsdccval? output pin ?high?, it should sample and latch the contents of this output pin (as a valid section dcc bit) into the ?section dcc hdlc? circuitry.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 99 ad6 rxsdccval o cmos receive ? section dcc output port ? dcc value indicator output pin: this output pin, along with the ?rxtohclk? and the ?rxsdcc? output pins function as the ?recei ve section dcc? output port of the xrt94l33. this output pin pulses ?high? co incident to when the ?receive section dcc? output port outputs a dcc bit via the ?rxsdcc? output pin. this output pin is updated upon t he falling edge of ?rxtohclk?. the section dcc hdlc controller circuitry that is interfaced to this output pin, the ?rxsdcc? and the ?rxtohclk? pins is suppose to do the following. it should continuously sample and m onitor the state of this output pin upon the rising edge of ?rxtohclk?. anytime the ?section dcc hdlc? circuitry samples this output pin being ?high?, it should sample and latch the data on the ?rxsdcc? output pin (as a valid section dcc bit) into the ?section dcc hdlc? circuitry. af4 rxe1f1e2val o cmos receive ? order wire output port ? e1f1e2 value indicator output pin: this output pin, along with the ?rxtohclk?, ?rxe1f1e2fp?, ?rxe1f1e2? and ?rxtohclk? output pins function as the ?receive ? order wire output port? of the xrt94l33. this output pin pulses ?high? coincident to when the ?receive ? order wire? output port outputs the contents of an e1, f1 or e2 byte, via the ?rxe1f1e2? output pin. this output pin is updated upon t he falling edge of ?rxtohclk?. the ?receive order-wire? circuitry, that is interfaced to this output pin, the ?rxe1f1e2? and the ?rxto hclk? pins is suppose to do the following. it should continuously sample and m onitor the state of this output pin upon the rising edge of ?rxtohclk?. anytime the ?receive order-wire? circuitry samples this output pin being ?high?, it should sample and latch the data on the ?rxe1f1e2? output pin (as a valid order-wire bit) into the ?receive order-wire? circuitry. ae6 rxpoh o cmos receive au-4/vc-4/sts-3c mapper poh processor block ? path overhead output port ? output pin: this output pin, along with the ?rxpohclk?, ?rxpohframe? and ?rxpohvalid? function as the ?a u-4/vc-4 mapper poh processor block ? poh output port. these pins serially output the poh data that have been received by the receive au-4/vc-4 mapper poh processor block (via the ?incoming? sts-3 data-stream). each bit, within the poh bytes is updated (via these output pi ns) upon the falling edge of ?rxpohclk?. as a consequence, external circuitry receiving this data, should sample this data upon the rising edge of ?rxpohclk?.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 100 ag4 rxpohclk o cmos receive au-4/vc-4/sts-3c mapper poh processor block ? path overhead output port ? clock output signal: this output pin, along with ?rxpoh?, ?rxpohframe? and ?rxpohvalid? function as the ?a u-4/vc-4 mapper poh processor block ? poh output port. these output pins function as the ?clock output? signals for the ?au-4/vc-4 mapper poh processor block? poh output port. the ?rxpoh?, ?rxpohframe? and ?rxpohvalid? output pins are updated upon the falling edge of this clock signal. as a consequence, the external circuitry should sample these signals upon the rising edge of this clock signal. ae7 rxpohframe o cmos receive au-4/vc-4/sts-3c mapper poh processor block ? path overhead output port ? frame boundary indicator: these output pins, along with the ?rxpoh?, rxpohclk? and ?rxpohvalid? output pins function as the ?au-4/vc-4 mapper poh processor block ? path overhead output port. these output pins will pulse ?high? coincident with the very first poh byte (j1), of a given sts-1 frame, is being output via the corresponding ?rxpoh? output pin. ad9 rxpohvalid o cmos receive au-4/vc-4/sts-3c mapper poh processor block ? path overhead output port ? valid poh data indicator: these output pins, along with ?rxpoh?, ?rxpohclk? and ?rxpohframe? function as the ?au-4/vc-4 mapper poh processor block ? path overhead output port. these output pins will toggle ?hig h? coincident with when valid poh data is being output via the ?rxpoh ? output pins. this output is updated upon the falling edge of rxpohclk. hence, external circuitry should sample these signals upon rising edge of ?rxpohclk?. af5 ag5 af8 rxpoh_0 rxpoh_1 rxpoh_2 o cmos receive sonet poh processor block ? path overhead output port ? output pin: these output pins, along with the ?rxpohclk_n?, ?rxpohframe_n? and ?rxpohvalid_n? function as the ?receive sonet poh processor block ? poh output port. these pins serially output the poh data that have been received by each of the receive sonet poh processor blocks (via the ?incoming? sts-3 data-stream). each bit, within the poh bytes is updated (via these output pi ns) upon the falling edge of ?rxpohclk_n?. as a consequence, external circuitry receiving this data, should sample this data upon the rising edge of ?rxpohclk_n?.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 101 ae8 ae9 ag6 rxpohclk_0 rxpohclk_1 rxpohclk_2 o cmos receive sonet poh processor block ? path overhead output port ? clock output signal: these output pins, along with ?rxpoh_n?, ?rxpohframe_n? and ?rxpohvalid_n? function as the ?receive sonet poh processor block ? poh output port. these output pins function as the ?clock output? signals for the ?receive sonet poh processor block ? poh output port. the ?rxpoh_n?, ?rxpohframe_n? and ?rxpohvalid_n? output pins are updated upon the falling edge of this clock signal. as a consequence, the external circuitry should sample these signals upon the rising edge of this clock signal. af6 ad10 ae10 rxpohframe_0 rxpohframe_1 rxpohframe_2 o cmos receive sonet poh processor block ? path overhead output port ? frame boundary indicator: these output pins, along with t he ?rxpoh_n?, rxpohclk_n? and ?rxpohvalid_n? output pins functi on as the ?receive sonet poh processor block ? path overhead output port. these output pins will pulse ?high? coincident with the very first poh byte (j1), of a given sts-1 frame, is being output via the corresponding ?rxpoh_n? output pin. ac10 af7 ac11 rxpohvalid_0 rxpohvalid_1 rxpohvalid_2 o cmos receive sonet poh processor block ? path overhead output port ? valid poh data indicator: these output pins, along with ?rxpoh_n?, ?rxpohclk_n? and ?rxpohframe_n? function as the ?receive sonet poh processor block ? path overhead output port. these output pins will toggle ?hig h? coincident with when valid poh data is being output via the ?rxpoh _n? output pins. this output is updated upon the falling edge of rxpohclk_n. hence, external circuitry should sample these signals upon rising edge of ?rxpohclk_n?. ad11 lof o cmos receive sts-3 lof (loss of frame) indicator: this output pin indicates whether or not the receive sts-3 toh processor block (within the device ) is currently declaring the lof defect condition as described below. low ? indicates that the receiv e sts-3 toh processor block is not currently declaring the lof defect condition. high ? indicates that the receive sts-3 toh processor block is currently declaring the lof defect condition. af9 sef o cmos receive sts-3 sef (severed errored frame) indicator: this output pin indicates whether or not the receive sts-3 toh processor block (within the device) is currently declaring the sef defect condition as described below. low ? indicates that the receiv e sts-3 toh processor block is not currently declaring t he sef defect condition. high ? indicates that the receive sts-3 toh processor block is currently declaring the sef defect condition.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 102 ag7 los o cmos receive sts-3 los (loss of signal) defect indicator: this output pin indicates whether or not the receive sts-3 toh processor block (within the device ) is currently declaring the los defect condition as described below. low ? indicates that the receiv e sts-3 toh processor block is not currently declaring the los defect condition. high ? indicates that the receive sts-3 toh processor block is currently declaring the los defect condition. g eneral p urpose i nput /o utput w25 gpi0_0 i/o ttl/cmos general purpose input/output pin: this input pin can be configured to function as either an input or output pin by writing the appropriate value into bit 0 (gpio_dir_0), within the ?operation general purpose input/output direction register ? 0? (address location = 0x014b). if this pin is configured to be an input pin the state of this pin can be monitored by reading the st ate of bit 0 (gpio_0) within the ?operation general purpose input/output register ? byte 0? (address location = 0x0147). if this pin is configured to be an output pin the state of this pin can be controlled by writing the appropriate value into bit 0 (gpio_0) within the ?operatio n general purpose input/output register ? byte 0? (address location = 0x0147). ac27 gpio_1 i/o ttl/cmos general purpose input/output pin this input pin can be configured to function as either an input or output pin by writing the appropriate value into bit 1 (gpio_dir_1), within the ?operation general purpose input/output direction register ? 0? (address location = 0x014b). if this pin is configured to be an input pin, then the state of this pin can be monitored by reading the state of bit 1 (gpio_1) within the ?operation general purpose inpu t/output register ? byte 0? (address location = 0x0147). if this pin is configured to be an output pin, t hen the state of this pin can be controlled by writing the appropriate value into bit 1 (gpio_1) within the ?operation general purpose input/output register ? byte 0? (address location = 0x0147).
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 103 v23 gpio_2 i/o ttl/cmos general purpose input/output pin this input pin can be configured to function as either an input or output pin by writing the appropriate value into bit 2 (gpio_dir_2), within the ?operation general purpose input/output direction register ? 0? (address location = 0x014b). if this pin is configured to be an input pin, then the state of this pin can be monitored by reading the state of bit 2 (gpio_2) within the ?operation general purpose inpu t/output register ? byte 0? (address location = 0x0147). if this pin is configured to be an output pin, t hen the state of this pin can be controlled by writing the appropriate value into bit 2 (gpio_2) within the ?operation general purpose input/output register ? byte 0? (address location = 0x0147). ab26 gpio_3 i/o ttl/cmos general purpose input/output pin this input pin can be configured to function as either an input or output pin by writing the appropriate value into bit 3 (gpio_dir_3), within the ?operation general purpose input/output direction register ? 0? (address location = 0x014b). if this pin is configured to be an input pin, then the state of this pin can be monitored by reading the state of bit 3 (gpio_3) within the ?operation general purpose inpu t/output register ? byte 0? (address location = 0x0147). if this pin is configured to be an output pin, t hen the state of this pin can be controlled by writing the appropriate value into bit 3 (gpio_3) within the ?operation general purpose input/output register ? byte 0? (address location = 0x0147). y25 gpio_4 i/o ttl/cmos general purpose input/output pin this input pin can be configured to function as either an input or output pin by writing the appropriate value into bit 4 (gpio_dir_4), within the ?operation general purpose input/output direction register ? 0? (address location = 0x014b). if this pin is configured to be an input pin, then the state of this pin can be monitored by reading the state of bit 4 (gpio_4) within the ?operation general purpose inpu t/output register ? byte 0? (address location = 0x0147). if this pin is configured to be an output pin, t hen the state of this pin can be controlled by writing the appropriate value into bit 4 (gpio_4) within the ?operation general purpose input/output register ? byte 0? (address location = 0x0147).
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 104 ac26 gpio_5 i/o ttl/cmos general purpose input/output pin this input pin can be configured to function as either an input or output pin by writing the appropriate value into bit 35(gpio_dir_5), within the ?operation general purpose input/output direction register ? 0? (address location = 0x014b). if this pin is configured to be an input pin, then the state of this pin can be monitored by reading the state of bit 5 (gpio_5) within the ?operation general purpose inpu t/output register ? byte 0? (address location = 0x0147). if this pin is configured to be an output pin, t hen the state of this pin can be controlled by writing the appropriate value into bit 5 (gpio_5) within the ?operation general purpose input/output register ? byte 0? (address location = 0x0147). w24 gpio_6 i/o ttl/cmos general purpose input/output pin this input pin can be configured to function as either an input or output pin by writing the appropriate value into bit 6 (gpio_dir_6), within the ?operation general purpose input/output direction register ? 0? (address location = 0x014b). if this pin is configured to be an input pin, then the state of this pin can be monitored by reading the state of bit 6 (gpio_6) within the ?operation general purpose inpu t/output register ? byte 0? (address location = 0x0147). if this pin is configured to be an output pin, t hen the state of this pin can be controlled by writing the appropriate value into bit 6 (gpio_6) within the ?operation general purpose input/output register ? byte 0? (address location = 0x0147). aa25 gpio_7 i/o ttl/cmos general purpose input/output pin this input pin can be configured to function as either an input or output pin by writing the appropriate value into bit 7 (gpio_dir_7), within the ?operation general purpose input/output direction register ? 0? (address location = 0x014b). if this pin is configured to be an input pin, then the state of this pin can be monitored by reading the state of bit 7 (gpio_7) within the ?operation general purpose inpu t/output register ? byte 0? (address location = 0x0147). if this pin is configured to be an output pin, t hen the state of this pin can be controlled by writing the appropriate value into bit 7 (gpio_7) within the ?operation general purpose input/output register ? byte 0? (address location = 0x0147).
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 105 c lock i nputs e7 refclk34 i ttl e3 reference clock input for the jitter attenuator within the ds3/e3 mapper block: to operate any of the channels (within the xrt94l33) in the e3 mode, apply a clock signal with a frequency of 34.368 20ppm to this input pin. this input pin functions as the timing reference for the ds3/e3/sts-1 jitter attenuator (within the ds3/e3 mapper block) for e3 applications. note: connect this pin to gnd if none of the channels of the xrt94l33 are to be operated in the e3 or if the xrt94l33 is to be operated in the sfm mode. d5 refclk51 i ttl sts-1 reference clock input for the jitter attenuator within the ds3/e3 mapper block. to operate any of the channels (within the xrt94l33) in the sts-1/stm-0 mode, apply a clock signal with a frequency of 51.84mhz 20ppm to this input pin. this input pin functions as the timing reference for the ds3/e3/sts-1 jitter attenuator (within the ds3/e3 mapper block) for sts-1 applications. notes: if the user intends to operate the xrt94l33 in the sfm mode, apply a 12.288mhz 20ppm clock signal to this input pin. if the user does not intend to operate any of the channels in the sts-1/stm-0 mode, connect this input pin to gnd . f7 refclk45 i ttl ds3 reference clock input for the jitter attenuator within the ds3/e3 mapper block: to operate any of the channels of the xrt94l33 in the ds3 mode, apply a clock signal with a frequency of 44.73620ppm to this input pin. this input pin functions as the timing reference for the ds3/e3/sts-1 jitter attenuator (within the ds3/e3 mapper block) for ds3 applications. if the user does not intend to operate any of the three (3) channels within the xrt94l33 in the ds3 mode, or if the user intends to configure the xrt94l33 to operate in the sfm mode, then tie this input pin to gnd. b oundary s can f5 tdo o cmos test data out: boundary scan test data output f4 tdi i ttl t est data in: boundary scan test data input note: this input pin should be pulled ?low? for normal operation. d3 trst i ttl jtag test reset input
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 106 e4 tck i ttl test clock: boundary scan clock input note: this input pin should be pulled ?low? for normal operation. e5 tms i ttl test mode select: boundary scan mode select input note: this input pin should be pulled ?low? for normal operation. f iltering c apacitors u6 rxcapp i analog external loop capacitor for receive pll: this pin connects to the positive side of the external capacitor, which is used to minimize jitter peaking. u5 rxcapn i analog external loop capacitor for receive pll: this pin connects to the negative side of the external capacitor, which is used to minimize jitter peaking. w6 rxcapp_r i anal0og external redundant loop capacitor for receive pll: this pin connects to the positive side of the external capacitor, which is used to minimize jitter peaking. w5 rxcapn_r i analog external redundant loop capacitor for receive pll: this pin connects to the negative side of the external capacitor, which is used to minimize jitter peaking. m iscellaneous p ins h5 refsel_l i ttl clock synthesizer block select: this input pin permits the user to configure the ?transmit sonet? circuitry (within the xrt94l33) to use either of the following clock signals as its timing source. a. the ?directly-applied? 19.44mhz clock signal, which is applied to the refttl input pin (p1) or, b. the output of the ?clock synthesizer? block (within the chip). setting this input pin ?high? configures the ?transmit sonet? circuitry within the xrt94l33 to use the ?clock synthesizer? block as its timing source. in this mode, the user can supply either a 19.44mhz, 38.88mhz, 51.84mhz or 77.76mhz clock signal to the refttl input pin. setting this input pin ?low? by-passes the ?clock synthesizer? block. in this case, the user must supply a 19.44mhz clock signal to the refttl input pin in order to insure proper performance.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 107 k4 sfm i ttl single frequency mode (sfm) select: this input pin permits the user to configure the three jitter attenuator blocks within the xrt94l33 to operate in the single- frequency mode (sfm). if the xrt94l33 has been configured to operate in the sfm mode, then the user only needs to supply a 12.288mhz clock signal to the refclk51 input pin. in this case, the user does not need to supply a 44.736mhz clock signal to the refclk45 input pin, nor a 34.368mhz clock signal to the refclk34 input pin. the sfm pll (within the xrt94l33) will internally synthesize the appropriate 44.736mhz, 34.368mhz or 51.84mhz clock si gnals, and will route these signals to the appropriate channels (within the chip) depending upon the data rate that they are configured to operate in. setting this input pin to a logic ?low? disables the single- frequency mode. in this mode, the user must supply all of the appropriate frequencies to the refclk34, refclk45 and refclk51 input pins. setting this input pin to a logic ?high? configures the xrt94l33 to operate in the single-frequency mode. j3 test mode i ttl test mode input pin: user should connect this input pin ?low? for normal operation. g2 fl_tstclk o cmos ja testing clock: this pin is used for ja testing purposes. j2 analog o analog analog output pin: this output analog pin is used for testing purposes. n1 vdctst1 o analog dc test pin: this pin is used for internal dc test, for example, it can be used to test for dc current, dc voltage. n2 vdctst2 o analog dc test pin: this pin is used for internal dc test, for example, it can be used to test for dc current, dc voltage.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 108 n o -c onnect p ins k1 n/c aa1 n/c v3 n/c ab1 n/c aa2 n/c ac1 n/c r1 n/c ab2 n/c ac2 n/c t1 n/c ac4 n/c ab5 n/c ad4 n/c ac5 n/c ab7 n/c ac6 n/c ac22 n/c ad24 n/c ab21 n/c ac23 n/c ab23 n/c ac24 n/c aa23 n/c e24 n/c f23 n/c d24 n/c e23 n/c f21 n/c e22 n/c
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 109 vdd (3.3v) n23 n25 v5 h2 l2 k3 h1 l5 u4 n3 t5 m5 analog vdd pins _ u3 r2 r6 c2 c1 j6 k6 w3 y3 ae1 ae2 af3 ab9 ab10 ab11 ab17 ab18 ab19 af25 ae26 w22 v22 u22 l22 k22 j22 c27 c26 b25 a25 f19 f18 f17 f11 f10 digital vdd
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 110 f9 a3 b3 d4 c4
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 111 g round g6 c3 a1 b1 af1 af2 aa6 ab6 ae3 ag1 ag2 ab13 ab14 ab15 ag26 af26 ab22 aa22 ae25 ag27 af27 t22 r22 p22 n22 m22 b27 b26 g22 f22 c25 a27 a26 f15 f14 f13 a2 b2 f6 v2 w4 y6 y5 y4 e6 v4 r5 digital ground
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 112 r3 p4 v6 l6 t4 n24 n26 r4 f1 k2 g1 l1 m6 n4 t6 j1 analog ground
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 113 1.0 xrt94l33 architecture the xrt94l33 can be configured to operate in any of the following modes for atm and ppp applications ? the 1-channel sts-3c and up to 2 channel ds3/e3 atm uni/ppp mode ? the 1-channel sts-3 (e.g., 3 channel of atm uni/ ppp over sts-1, which is in-turn mapped into sts-3 mode ? the 1-channel sts-3/stm-1 (e.g., 3 channels of at m/ppp over ds3/e3, which is turn mapped into sts- 3 mode. the basic functional architecture of the xrt94l33, when it is configured to operate in either of these modes will be presented below. 1.1 functional architecture of the xrt94l 33 ? 1 channel sts-3c atm uni/ppp mode if the xrt94l33 has been configured to operate in the ?1 channel sts-3c atm uni/ppp? mode, then it will have the ?functional architecture? as is presented below in figure 1. figure 1: the functional block diagram of the xrt94l33 when it has been configured to operate in the 1-channel sts-3c atm uni/ppp mode transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3 toh processor block receive sts-3 toh processor block transmit sts-3 toh processor block transmit sts-3 toh processor block receive sts-3c poh processor block receive sts-3c poh processor block transmit sts-3c poh processor block transmit sts-3c poh processor block sts-3 telecom bus interface block sts-3 telecom bus interface block sts-3 pecl interface block sts-3 pecl interface block sts-3 cdr block sts-3 cdr block xrt94l33 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 114 figure 1 indicates that the xrt94l33 consis ts of the following functional blocks. ? the receive sts-3 pecl interface block ? the receive sts-3 telecom bus interface block ? the receive sts-3 toh processor block ? the receive sts-3c poh processor block ? the receive atm cell processor block ? the receive utopia interface block ? the receive ppp packet processor block ? the receive pos-phy interface block ? the transmit pos-phy interface block ? the transmit atm cell processor block ? the transmit ppp packet processor block ? the transmit sts-3c poh processor block ? the transmit sts-3 toh processor block ? the transmit sts-3 telecom bus interface block ? the transmit sts-3 pecl interface block each of these functional blocks is briefly discussed below. these functional blocks will be discussed in considerable detail throughout this data sheet. 1.1.1 t he c lock s ynthesizer b lock the purpose of the clock synthesizer block is to synthesize a 19.44mhz and a 155.52mhz clock signal from an externally supplied 19.44mhz reference clock signal. the transmit sts-3 toh and the transmit sts-3c poh processor blocks will use these clock signals as its timing source, for transmitting the outbound sts-3 data ei ther via the pecl interface (e.g., to the optical transceiver) or via the telecom bus in terface, to the remote terminal. 1.1.2 t he r eceive sts-3 pecl i nterface and cdr b lock the purpose of the receive sts-3 pecl interface and cdr block is to perform the following functions. ? to receive an sts-3 electrical signal (which is of the pecl format) from either a system back-plane or from an optical transceiver. ? as the receive sts-3 pecl interface block receives th is electrical (data) signal, it will route this data- stream to the ?sts-3 clock and data recovery (cdr ) block. this sts-3 cd r block will then generate a 155.52mhz clock and corresponding data signal, which will be routed to the receive sts-3 toh processor block for further processing.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 115 1.1.3 t he r eceive sts-3 toh p rocessor b lock the purpose of the ?receive sts-3 toh processor? block is to perform the following functions. ? to receive an sts-3 signal from the remote terminal via optical fiber and a pecl interface, or via the ?receive sts-3 telecom bus interface. ? to declare and clear the los, sef, lof and ais-l defect conditions. ? to declare and clear the rdi-l, sd and sf defect conditions. ? to optionally transmit the ais-p indicator (downstr eam, towards the receive sts-3c poh processor block) upon declaration of the ais-l, los, lof, sd or sf defect conditions. ? to compute and verify the b1 and b2 bytes of the incoming sts-3 signal. ? to detect and increment performance monitor regist ers anytime it detects any b1 and b2 byte errors. ? to receive and process section trace messages via the j0 byte. ? to terminate the transport overhead (toh) within the incoming sts-3 signal. ? to detect and increment performance monitor registers anytime it det ects any rei-l events. ? to receive and process messages via the j0 byte. ? to terminate the transport overhead (toh) within the incoming sts-3 signal. ? to the resulting sts-3c spe data-stream to the receive sts-3c poh processor block. 1.1.4 t he r eceive sts-3 c poh p rocessor b lock the purpose of the ?receive sts-3c poh processo r? block is to perform the following functions. ? to receive the sts-3c signal (originally extracted from the incoming sts-3 signal) to terminate the path overhead (poh). ? to declare and clear lop-p, ais-p, uneq-p, plm-p, tim-p, and the rdi-p defect conditions. ? to optionally transmit the ais-p indicator, in the down-stream direction (towards the receive atm cell or receive ppp packet processor blocks) anytime (and for the duration that) the receive sts-3c poh processor declares the ais-p, lop-p, uneq-p, plm-p or tim-p defect conditions ? to declare and clear the lop-c and ais-c defect condition. ? to compute and verify the b3 byte of the incoming sts-3 spe. ? to detect and increment performance monitor registers anytime it detects b3 byte errors in the incoming sts-3c spe data-stream. ? to detect and increment performance monitor registers anytime it detects any rei-p events. ? to receive and process path trace messages via the j1 byte. ? to route the sts-3c spe data to the receive atm cell processor or receive ppp packet processor blocks for further processing.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 116 1.1.5 t he r eceive atm c ell p rocessor b lock the purpose of the ?receive atm cell processor? bloc k is to extract out the data (being carried by the incoming sts-3c spe data-str eam) and to perform the fo llowing operations on it. ? cell delineation ? hec byte verification ? idle cell filtering ? user cell filtering ? to receive cells, with ?user-specified? header bytes and to load them into the ?receive cell extraction memory buffer? (where they can be read out and accessed by the microprocessor interface) ? to read out a ?user-specified? atm cell (which is residing in the receive cell insertion buffer) and to insert this cell into the ?receive atm cell? traffic. ? to route all filtered cells to t he ?receive atm cell buffer? (where it will be made available to the atm layer processor via the receive utopia interface block). 1.1.6 t he r eceive utopia i nterface b lock the purpose of the receive utopia in terface block is to provide a standard utopia level 1, 2 or 3 interface to the atm layer processor; for reading out the contents of all atm cells that are written into the ?receive atm cell buffer?. the receive utopia interface block can be configured to operate with eit her an 8 or 16-bit wide ?receive utopia data? bus. note: the receive utopia interface block supports ?utopi a level 3? from a signaling stand-point. the receive utopia interface block within the xrt94l33 still only supports a 16-bit wide (not 32-bit wide) utopia bus and only operates up to 50mhz (not 100mhz). 1.1.7 t he t ransmit utopia i nterface b lock the purpose of the transmit utopia interface block is to provide a standard utopia level 1, 2 or 3 interface to the atm layer processor, for writing in t he contents of all ?valid? atm cells, into the ?transmit cell buffer?. the transmit utopia interface block can be configured to operate with either an 8 or 16-bit wide ?transmit utopia data? bus. note: the transmit utopia interface block supports ?utopia level 3? from a signaling stand-point. the receive utopia interface block within the xrt94l33 still only supports a 16-bit wide (not 32-bit wide) utopia bus and only operates up to 50mhz (not 100mhz).
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 117 1.1.8 t he t ransmit atm c ell p rocessor b lock the purpose of the ?transmit atm cell processor? block is to read out the contents of ?user? cells that have been written into the ?txfifo? (via the transmit utopia interface block); and perform the following functions. ? optionally compute and verify the hec byte of each cell written into the ?transmit cell buffer? ? to optionally discard all incoming atm cells that contain hec byte errors. ? optionally compute and insert the hec byte into the fifth octet position, within each cell written into the ?transmit atm cell buffer?. ? to optionally filter user cells (t hat are read out from the txfifo) by ei ther discarding these user cells, or by replicating them and routing t he copies of these cells to the transmit cell extraction buffer. ? to insert cells (residing within th e transmit cell insertion buffer) into the transmit data path anytime the txfifo is depleted of user cells. ? generate idle cells, anytime the txfifo and the tr ansmit cell insertion buffer are depleted of ?user? cells. ? to route the composite stream of ?valid? and ?idle? cells to the transmit sts-3c poh processor block. 1.1.9 t he t ransmit sts-3 c poh p rocessor b lock the purpose of the ?transmit sts-3c poh processor? block is to perform the following functions. ? to receive atm cell or ppp data from the tr ansmit atm cell processor or transmit ppp packet processor blocks and to map this data into an sts-3c spe data-stream. ? to automatically transmit the rdi-p indicator (to the remote pte) upon detection of the following conditions, by the receive sts-3c poh processor block. a. ais-p b. lop-p c. uneq-p d. plm-p e. tim-p ? to automatically transmit the rdi-p indicator (to t he remote pte) anytime (and for the duration that) the corresponding receive atm cell processor block declares the lcd-p (loss of cell delineation) defect condition. ? to transmit the rdi-p indicator upon software control. ? to transmit the rei-p indicator (t o the remote pte) upon detection of b3 byte errors by the corresponding receive sts-3c poh processor block. ? to transmit the rei-p indicator upon software control. ? to compute the bip-8 value over the entire sts-3c spe and to insert this value into the ?b3-byte? position within the very next outbound sts-3c spe. ? to transmit the ais-p indicator (under software control).
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 118 1.1.10 t he t ransmit sts-3/12 toh p rocessor b lock the purpose of the ?transmit sts-3 toh processor? block is to perform the following functions. ? to generate and insert the toh (for the ?outbound? sts-3c signal) prior to transmission to the remote lte. ? to automatically transmit the rdi-l indicator (to t he remote lte) upon detection of the following defect conditions by the corresponding re ceive sts-3 toh processor block. a. los b. lof c. ais-l d. sd e. sf ? to transmit the rdi-l indicator upon software control. ? to automatically transmit the rei-l indicator (to th e remote lte) upon detection of b2 byte errors by the receive sts-3 toh processor block. ? to transmit the rei-l indicator upon software control. ? to transmit the ais-l indicator (to the remote lte) upon software command. 1.1.11 t he t ransmit sts-3 pecl i nterface b lock the purpose of the transmit sts-3 pecl interface bloc k is to accept sts-3 data from the transmit sts-3 toh processor block and to perform the following functions on this signal. ? converting this ?out bound? cmos-level signal into the lvpecl format. ? to output this sts-3 pecl signal to either the sy stem back-plane (for transmission to a ?concentrator? board) or to an optical transceiver, for transmission to remote terminal equipment. 1.2 functional architecture of the xrt 94l33 ? 1 channel sts-3 atm uni/ppp mode if the xrt94l33 has been c onfigured to operate in the ?1-channel sts-3 atm uni/ ppp? mode, then it will have the ?functional architecture? as is presented below in figure 2
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 119 figure 2 the functional block diagram of the xrt94l33 when it has been configured to operate in the 1-channel sts-3 atm uni/ppp mode transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell p rocessor block receive atm cell p rocessor block receive atm cell p rocessor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3 toh processor block receive sts-3 toh processor block transmit sts-3 toh processor block transmit sts-3 toh processor block receive sonet poh processor block receive sonet poh processor block transmit sonet poh processor block transmit sonet poh processor block sts-3/12 te lecom bus interface block sts-3/12 te lecom bus interface block sts-3/12 pecl interface block sts-3/12 pecl interface block sts-3/12 cdr block sts-3/12 cdr block xrt94l33 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block from channels 1 and 2 to channels 1 and 2 figure 2 indicates that the xrt94l33 consis ts of the following functional blocks. ? the receive sts-3 pecl interface block ? the receive sts-3 telecom bus interface block ? the receive sts-3 toh processor block ? the receive sonet poh processor block ? the receive atm cell processor block ? the receive utopia interface block ? the receive ppp packet processor block ? the receive pos-phy interface block ? the transmit pos-phy interface block ? the transmit atm cell processor block ? the transmit ppp packet processor block ? the transmit sonet poh processor block ? the transmit sts-3 toh processor block ? the transmit sts-3 telecom bus interface block ? the transmit sts-3 pecl interface block
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 120 each of these functional blocks is briefly discusse d below. these functional blocks will be discussed in considerable detail throughout this data sheet. 1.2.1 t he c lock s ynthesizer b lock the purpose of the clock synthesizer block is to synthesize a 19.44mhz and a 155.52mhz clock signal from an externally supplied 19.44mhz reference clock signal. the transmit sts-3 toh and the transmit sts-3c poh processor blocks will use these clock signals as its timing source, for transmitting the outbound sts-3 data ei ther via the pecl interface (e.g., to the optical transceiver) or via the telecom bus in terface, to the remote terminal. 1.2.2 t he r eceive sts-3 pecl i nterface and cdr b lock the purpose of the receive sts-3 pecl interface and cdr block is to perform the following functions. ? to receive an sts-3 electrical signal (which is of the pecl format) from either a system back-plane or from an optical transceiver. ? as the receive sts-3 pecl interface block receives th is electrical (data) signal, it will route this data- stream to the ?sts-3 clock and data recovery (cdr ) block. this sts-3 cd r block will then generate a 155.52mhz clock and corresponding data signal, which will be routed to the receive sts-3 toh processor block for further processing. 1.2.3 t he r eceive sts-3 toh p rocessor b lock the purpose of the ?receive sts-3 toh processor? block is to perform the following functions. ? to receive an sts-3 signal from the remote terminal via optical fiber and a pecl interface, or via the ?receive sts-3 telecom bus interface. ? to declare and clear the los, sef, lof and ais-l defect conditions. ? to declare and clear the rdi-l, sd and sf defect conditions. ? to optionally transmit the ais-p indicator (downstr eam, towards the receive sts-3c poh processor block) upon declaration of the ais-l, los, lof, sd or sf defect conditions. ? to compute and verify the b1 and b2 bytes of the incoming sts-3 signal. ? to detect and increment performance monitor regist ers anytime it detects any b1 and b2 byte errors. ? to receive and process section trace messages via the j0 byte. ? to terminate the transport overhead (toh) within the incoming sts-3 signal. ? to detect and increment performance monitor registers anytime it det ects any rei-l events. ? to receive and process messages via the j0 byte. ? to terminate the transport overhead (toh) within the incoming sts-3 signal. ? to byte de-inter leave the sts-3 signal into 3 sts-1 spe data-st reams, and to route the resulting sts-1 spe data-stream to each of the three (3 ) receive sonet poh processor block. 1.2.4 t he r eceive sonet poh p rocessor b lock the purpose of the ?receive sonet poh processor? block is to perform the following functions. ? to receive one of the three sts-1 signal (originally extracted from the incoming sts-3 signal) to terminate the path overhead (poh). ? to declare and clear lop-p, ais-p, uneq-p, plm-p, tim-p, and the rdi-p defect conditions.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 121 ? to optionally transmit the ais-p indicator, in the down-stream direction (towards the receive atm cell or receive ppp packet processor blocks) anytime (and for the duration that) the receive sonet poh processor declares the ais-p, lop-p, uneq-p, plm-p or tim-p defect conditions ? to declare and clear the lop-c and ais-c defect condition. ? to compute and verify the b3 byte of the incoming sts-3 spe. ? to detect and increment performance monitor registers anytime it detects b3 byte errors in the incoming sts-1 spe data-stream. ? to detect and increment performance monitor registers anytime it detects any rei-p events. ? to receive and process path trace messages via the j1 byte. ? to route the sts-1 spe data to the receive atm ce ll processor or receive ppp packet processor blocks for further processing. 1.2.5 t he r eceive atm c ell p rocessor b lock the purpose of the ?receive atm cell processor? bloc k is to extract out the data (being carried by its corresponding incoming sts-1 spe data-stream) and to perform the following operations on it. ? cell delineation ? hec byte verification ? idle cell filtering ? user cell filtering ? to receive cells, with ?user-specified? header bytes and to load them into the ?receive cell extraction memory buffer? (where they can be read out and accessed by the microprocessor interface) ? to read out a ?user-specified? atm cell (which is residing in the receive cell insertion buffer) and to insert this cell into the ?receive atm cell? traffic. ? to route all filtered cells to t he ?receive atm cell buffer? (where it will be made available to the atm layer processor via the receive utopia interface block). 1.2.6 t he r eceive utopia i nterface b lock the purpose of the receive utopia in terface block is to provide a standard utopia level 1, 2 or 3 interface to the atm layer processor; for reading out the contents of all atm cells that are written into the ?receive atm cell buffer?. the receive utopia interface block can be configured to operate with eit her an 8 or 16-bit wide ?receive utopia data? bus. note: the receive utopia interface block supports ?utopi a level 3? from a signaling stand-point. the receive utopia interface block within the xrt94l33 still only supports a 16-bit wide (not 32-bit wide) utopia bus and only operates up to 50mhz (not 100mhz). 1.2.7 t he t ransmit utopia i nterface b lock the purpose of the transmit utopia interface block is to provide a standard utopia level 1, 2 or 3 interface to the atm layer processor, for writing in t he contents of all ?valid? atm cells, into the ?transmit cell buffer?. the transmit utopia interface block can be configured to operate with either an 8 or 16-bit wide ?transmit utopia data? bus. note: the transmit utopia interface block supports ?utopia level 3? from a signaling stand-point. the receive utopia interface block within the xrt94l33 still only supports a 16-bit wide (not 32-bit wide) utopia bus and only operates up to 50mhz (not 100mhz).
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 122 1.2.8 t he t ransmit atm c ell p rocessor b lock the purpose of the ?transmit atm cell processor? block is to read out the contents of ?user? cells that have been written into the ?txfifo? (via the transmit utopia interface block); and perform the following functions. ? optionally compute and verify the hec byte of each cell written into the ?transmit cell buffer? ? to optionally discard all incoming atm cells that contain hec byte errors. ? optionally compute and insert the hec byte into the fifth octet position, within each cell written into the ?transmit atm cell buffer?. ? to optionally filter user cells (t hat are read out from the txfifo) by ei ther discarding these user cells, or by replicating them and routing t he copies of these cells to the transmit cell extraction buffer. ? to insert cells (residing within th e transmit cell insertion buffer) into the transmit data path anytime the txfifo is depleted of user cells. ? generate idle cells, anytime the txfifo and the tr ansmit cell insertion buffer are depleted of ?user? cells. ? to route the composite stream of ?valid? and ?idl e? cells to the transmit sonet poh processor block. 1.2.9 t he t ransmit sonet poh p rocessor b lock the purpose of the ?transmit sonet poh processor? block is to perform the following functions. ? to receive atm cell or ppp data from its corres ponding transmit atm cell proc essor or transmit ppp packet processor blocks and to map th is data into an sts-1 spe data-stream. ? to automatically transmit the rdi-p indicator (to the remote pte) upon detection of the following conditions, by the corresponding re ceive sonet poh processor block. a. ais-p b. lop-p c. uneq-p d. plm-p e. tim-p ? to automatically transmit the rdi-p indicator (to t he remote pte) anytime (and for the duration that) the corresponding receive atm cell processor block declares the lcd-p (loss of cell delineation) defect condition. ? to transmit the rdi-p indicator upon software control. ? to transmit the rei-p indicator (to the remote pte) upon detection of b3 byte errors by the corresponding receive sonet poh processor block. ? to transmit the rei-p indicator upon software control. ? to compute the bip-8 value over the entire sts-1 spe and to insert this value in to the ?b3-byte? position within the very next outbound sts-1 spe. ? to transmit the ais-p indicator (under software control).
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 123 1.2.10 t he t ransmit sts-3 toh p rocessor b lock the purpose of the ?transmit sts-3 toh processor? block is to perform the following functions. ? to generate and insert the toh (for the ?outbound? sts-3 signal) prior to transmission to the remote lte. ? to automatically transmit the rdi-l indicator (to t he remote lte) upon detection of the following defect conditions by the corresponding re ceive sts-3 toh processor block. a. los b. lof c. ais-l d. sd e. sf ? to transmit the rdi-l indicator upon software control. ? to automatically transmit the rei-l indicator (to th e remote lte) upon detection of b2 byte errors by the receive sts-3 toh processor block. ? to transmit the rei-l indicator upon software control. ? to transmit the ais-l indicator (to the remote lte) upon software command. 1.2.11 t he t ransmit sts-3 pecl i nterface b lock the purpose of the transmit sts-3 pecl interface bloc k is to accept sts-3 data from the transmit sts-3 toh processor block and to perform the following functions on this signal. ? converting this ?out bound? cmos-level signal into the lvpecl format. ? to output this sts-3 pecl signal to either the sy stem back-plane (for transmission to a ?concentrator? board) or to an optical transceiver, for transmission to remote terminal equipment. 1.3 the microprocessor interface the purpose of the microprocessor inte rface block is to support the follo wing operations between the user?s microprocessor/microcontroller and the xrt94l33. ? writing/loading configuration information into t he ?on-chip? command registers; within the xrt94l33. ? reading out the state of various bit-fields, reflecting alarm conditions. ? writing in the contents of ?outbound? j0 (section trace) messages into the ?transmit j0 (section trace) message? buffer. ? reading out the contents of ?inbound? j0 messages from the ?receive j0 (section trace) message? buffer. ? writing in the contents of ?outbo und? j1 (path trace) messages into the ?transmit j1 (path trace) message? buffer. ? reading out the contents of ?inbound? j1 messages from the ?receive j1 (path trace) message? buffer. ? writing the contents of ?outbound? atm (oam) cells into the transmit cell inse rtion memory within the transmit atm cell processor block ? reading the contents of certain ?outbound? atm cells from the transmit cell extraction memory within the transmit atm cell processor block. ? reading the contents of ?inbound? atm (oam) cells from the receive cell extraction memory within the receive atm cell processor block.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 124 ? servicing of various interrupts. each of these operations (between the microprocessor and the xrt94l33) will be discussed in some detail, throughout this data sheet. figure 3 simple block diagram of microprocessor interface block of xrt94l33 a[14:0] wrb _rw rdb _ds csb* ale_as reset* int* d[7:0] rdy _ dtck microprocessor interface block ptype [2:0] a[14:0] wrb _rw rdb _ds csb* ale_as reset* int* d[7:0] rdy _ dtck microprocessor interface block ptype [2:0] 1.3.1 t he m icroprocessor i nterface s ignals the xrt94l33 may be configured into a wide variety of different operating modes and have its performance monitored by software through a microprocessor , using data, address and control signals. the c/ p configures the xrt94l33 (into a desired oper ating mode) by writing data into specific addressable, on-chip ?read/wr ite? registers; or on-chip ram. the microprocessor interface provides the signals which are required for a general purpose microprocessor to read or write data into these registers. the microprocessor interface also supports ?polle d? and interrupt driven environments. these interface signals are described below in tables 1, 2, and 3. the microprocessor interface within the xrt94l33 can be configured to operate in two basic modes. ? the intel asynchronous mode, and ? the power pc 403 mode each of these microprocessor interface modes is described in detail below. 1.3.1.1 t he i ntel a synchronous m ode : whenever the microprocessor interf ace has been configured to operate in the ?intel asynchronous? mode, then some of the these control signals function in a manner as required by the ?intel 80xx? family of microprocessors. presents a brief description of each of the micropro cessor interface pins whe never the microprocessor interface has been configured to operate in the ?intel asynchronous? mode.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 125 table 1 description of the microprocessor interface pins whenever the microprocessor interface has been configured to operate in the intel asynchronous mode p in n ame p in # t ype d escription d[7:0] i/o bi-directional data bus input/output pins for on-chip register and buffer read or write operation. this byte-wide data bus carries all data that is being written into or read form the xrt94l33. a[15:0] i sixteen bit address bus input pins: this 16-bit address bus permits the user to select an on-chip register or buffer location to be the ?target? address for the current read or write operation. cs* i chip select input pin: this ?active-low? signal selects the microprocessor interface of the xrt94l33 and enables read/write operations with on-chip registers and buffer locations. int* o interrupt request output pin: this open-drain/active-low output signal will inform the local microprocessor/microcontroller that the xr t94l33 has a pending interrupt request. under normal conditions this output pin will be at a logic ?high? level. however, this output pin will toggle ?low? whenever the xrt94l33 has a pending interrupt request that needs servicing. this output pin will remain ?low? until all pending interrupt requests have been serviced. please see section _ for more information on servicing interrupts. ale_as i address-latch enable : this ?active-high? signal is used to latch the contents on the ad dress bus, a[15:0]. the contents of the address bus are latched into the a[15:0] inputs on the falling edge of ale_as. the contents of the address bus will only be latched into the xrt94l33 circuitry if the cs* input pin is asserted (e.g., pulled ?low?). rd_ds i read strobe signal : this ?active-low? input functions as the read signal from the local p. when this signal goes ?low?, the xrt94l33 microprocessor interface will respond by placing the contents of the addressed register on the data bus pins (d[7:0]). the data bus will be ?tri-stated? once this input signal returns ?high?. wr_rw i write strobe signal : this ?active-low? input functions as the write signal from the local p. the contents of the data bus (d[7:0]) will be written in to the addressed regist er (via a[15:0]), on the rising edge of this signal. the xrt94l33 supports a wide variety of microprocessor types, including intel and motorola types of microprocessors. when the microprocessor interface is operating in the ?motorola? mode, then some of the control signals function in a manner as required by the motorola 68000 family of microprocessors. likewise, when the microprocessor interface is operating in the ?intel? mode, then some of these control signals function in a manner as required by the intel 80xx family of microprocessorstable 2 lists and describes those microprocessor interface signals whose role is
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 126 constant across the two modes. error! reference source not found. describes the role of some of these signals when the microprocessor interface is operating in the intel mode. likewise
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 127 table 4 describes the role of these signals when the mi croprocessor interface is operating in the motorola mode. table 2 description of the microprocessor interface si gnals that exhibit constant roles in both the ?intel? and ?motorola? modes. p in n ame t ype d escription d[7:0] i/o bi-directional data bus for register read or write operations. this byte wide carries all data that is being written into or read from the xrt94l33. a[14:0] i fourteen bit address bus input: this nine bit address bus is provided to allow the user to select an on-chip register or on-chip ram location. cs* i chip select input. this ?active low? signal selects the micropr ocessor interface of the xrt94l33 and enables read/write operations with the on- chip registers/on-chip ram. int* o interrupt request output this ?open-drain/active-low? output signal will inform the local p that the xrt94l33 has an interrupt condition that needs servicing. table 3 pin description of microprocessor interface signals - while the microprocessor interface is operating in the intel mode. p in n ame e quivalent p in in i ntel e nvironment t ype d escription ale_as ale i address-latch enable: this ?active-high? signal is used to latch the contents on the address bus, a[8:0]. t he contents of the address bus are latched into the a[8:0] inputs on the falling edge of ale_as. additionally, this signal can be used to indicate the start of a burst cycle. rdb_ds rd* i read signal: this ?active-low? input functi ons as the read signal from the local p. when this signal goes ?low?, the xrt94l33 microprocessor interface will place the contents of the addressed register on the data bus pins (d[7:0]). the data bus will be ?tri-stated? once this input signal returns ?high?. wrb_rw wr* i write signal: this ?active-low? input functions as the write signal from the local p. the contents of the data bus (d[7:0]) will be written into the addressed register (via a[8:0]), on the rising edge of this signal. rdy_dtck ready* o ready output: this ?active-low? signal is provided by the xrt94l33, and indicates that the current read or write cycle is to be extended until this signal is asserted. the local p will typically insert ?wait? states until this signal is asserted. this output wi ll toggle ?low? when the device is ready for the next read or write cycle.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 128 table 4 pin description of the microprocessor inte rface signals while the microprocessor interface is operating in the motorola mode p in n ame e quivalent p in in m otorola e nvironment t ype d escription ale_a s as* i address strobe: this ?active-low? signal is used to latch the contents on the address bus input pins: a[14:0] into the mi croprocessor interface circuitry. the contents of the address bus are latched into the xrt94l33 on the rising edge of the ale_as signal. this signal can also be used to indicate the start of a burst cycle. rdb_d s ds* i data strobe: this signal latches the contents of the bi-directional data bus pins into the addressed register within the xrt94l33 during a write cycle. wrb_ rw r/w* i read/write* input: when this pin is ?high?, it indicates a read cycle. when this pin is ?low?, it indicates a write cycle. rdy_dt ck dtack* o data transfer acknowledge: the xrt94l33 asserts dtack* in order to inform the cpu that the present read or write cycle is nearly complete. the 68000 family of cpus requires this signal from its peripheral devices, in order to quickly and properly complete a read or write cycle. 1.3.2 i nterfacing the xrt94l33 to the c/ p over via the m icroprocessor i nterface b lock the microprocessor interface block, within the xrt94l33 is very flexible and provides the following options to the user. ? to interface the xrt94l33 to a c/ p over an 8-bit-wide bi-directional data bus. ? to interface the xrt94l33 to a wide variety of microprocessor interface types ? to transfer data (between the xrt94l33 ic and the c/ p) via the programmed i/o mode. each of the options is discussed in detail below. se ction _ will discuss data access (e.g., programmed i/o and burst) mode when interfaced to both motorola-type and intel-type c/ p. 1.3.2.1 s electing the a ppropriate m icroprocessor i nterface m ode the user can configure the microprocessor interface, within the xrt94l33, to support a wide-variety of microprocessor interface modes. the user can accomplish this by setting the ptype[2:0] input pins to the appropriate setting as listed below. table 5 settings for the ptype[2:0] and the corresponding microprocessor interface modes pt ype [2:0] m icroprocessor i nterface m ode 000 68hc11, 8051, 80c188 001 motorola ? 68000 family 010 intel x86 family 011 intel i960 100 idt3051/52 101 power pc 403 this revision of the xrt94l33 data sheet discusses the motorola and intel x86 modes in detail. the remaining microprocessor interfac e modes will be discussed in a la ter revision of this data sheet.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 129 1.3.2.2 d ata a ccess m odes as mentioned earlier, the microprocessor interface bl ock supports data transfer between the xrt94l33 and the c/ p (e.g., ?read? and ?write? operations) via two modes: the ?programmed i/o? and the ?burst? modes. programmed i/o access is discussed within this revision of the data sheet. burst mode access will be discussed in the next revision of this data sheet. 1.3.2.3 d ata a ccess using p rogrammed i/o ?programmed i/o? is the conventional manner in which a microprocessor exchanges data with a peripheral device. however, it is also the slowest met hod of data exchange between the xrt94l33 and the c/ p; as will be described in this text. the next two sections present detailed informat ion on programmed i/o access, when the xrt94l33 is operating in the ?intel mode ? and in the ?motorola mode?. 1.3.3 p rogrammed i/o a ccess in the ?i ntel ? m ode if the xrt94l33 is interfaced to an ?intel-type? c/ p (e.g., the 80x86 family, etc.), then it should be configured to operate in the ?intel? mode (by tying the ?moto? pin to ground). intel-type ?read? and ?write? operations are described below. 1.3.3.1 t he i ntel m ode r ead c ycle whenever an intel-type c/ p wishes to read the contents of a register or some location within the transmit or receive extraction memory or the j0/j1 message bu ffers, within the xrt94l33, it should do the following. 1. place the address of the ?target? register or buffer location (wit hin the uni) on the a ddress bus input pins a[14:0]. 2. while the c/ p is placing this address value on the address bus, the address decoding circuitry (within the user?s system) should assert the cs * (chip select) pin of the xrt94l33, by toggling it ?low?. this action enables further communication between the c/ p and the xrt94l33 microprocessor interface block. 3. toggle the ale_as (address latch enable) input pin ?high?. this step enables the ?address bus? input drivers, within the microprocessor interface block of the xrt94l33. 4. after allowing the data on the address bus pins to settle (by waiting the appropriate ?address? data setup time?), the c/ p should toggle the ale_as pin ?low?. this step causes the xrt94l33 to ?latch? the contents of the ?address bus? into its internal circuitry. at th is point, the address of the register or buffer locations within the xrt94l33, has now been selected. 5. next, the c/ p should indicate that this current bus cycle is a ?read? operation by toggling the rdb_ds (read strobe) input pin ?low?. this action also enabl es the bi-directional data bus output drivers of the xrt94l33. at this point, the ?bi-directional? data bus ou tput drivers will proceed to drive the contents of the ?latched addressed? register (or buffer locati on) onto the bi-directional data bus, d[7:0]. 6. immediately after the c/ p toggles the ?read strobe? signal ?low?, the xrt94l33 will toggle the rdy_dtck output pin ?low?. the xrt94 l33 does this in order to inform the c/ p that the data (to be read from the data bus) is ?not ready? to be ?latched? into the c/ p. 7. after some settling time, the data on the ?bi-di rectional? data bus will stabilize and can be read by the c/ p. the xrt94l33 will indicate that this data c an be read by toggling the rdy_dtck (ready) signal ?high?. 8. after the c/ p detects the rdy_dtck signal (from the xrt9 4l33 uni), it can then terminate the read cycle by toggling the rdb_ds (read strobe) input pin ?high?. figure 4 presents a timing diagram which illustrates the behavior of the mi croprocessor inte rface signals, during an ?intel-type? progr ammed i/o read operation.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 130 figure 4 behavior of microprocessor interface signa ls during an ?intel-type? programmed i/o read operation ale_as rdb_ds a[14:0] cs* d[7:0] rdy_dtck not valid valid address of target register wr b _r w ale_as rdb_ds a[14:0] cs* d[7:0] rdy_dtck not valid valid address of target register wr b _r w wr b _r w 1.3.3.2 t he i ntel m ode w rite c ycle whenever an intel-type c/ p wishes to write a byte or word of data into a register or buffer location, within the xrt94l33, it should do the following. 1. assert the ale_as (address latch enable) input pin by toggling it ?high?. when the c/ p asserts the ale_as input pin, it enables the ?address bus input drivers? within the xrt94l33 chip. 2. place the address of the ?target? register or buffer location with in the xrt94l33, on the address bus input pins, a[14:0]. 3. while the c/ p is placing this address value onto the address bus, the address decoding circuitry (within the user?s system) should assert the cs* input pin of the xrt94l33 by toggl ing it ?low?. this step enables further communication between the c/ p and the xrt94l33 microprocessor interface block. 4. after allowing the data on the address bus pins to settle (by waiting the appropriate ?address setup? time); the c/ p should toggle the ale_as input pin ?low?. this step causes the xrt94l33 to ?latch? the contents of the ?address bus? into its internal circuitry. at this point, the address of the register or buffer location within the xrt94l33, has now been selected. 5. next, the c/ p should indicate that this current bus cycl e is a ?write? operation; by toggling the wrb_rw (write strobe) input pin ?low?. this action al so enables the ?bi-directional ? data bus input drivers of the xrt94l33. 6. the c/ p should then place the byte or word that it int ends to write into the ?target? register, on the bi- directional data bus, d[7:0]. 7. after waiting the appropriate amount of time, for the data (on the bi-directional data bus) to settle; the c/ p should toggle the wrb_rw (write strobe) input pin ?high?. this action accomplishes two things: a. it latches the contents of the bi-directional dat a bus into the xrt94l33 microprocessor interface block. b. it terminates the write cycle. figure 5 presents a timing diagram which illustrates the behavior of the mi croprocessor inte rface signals, during an ?intel-type? progra mmed i/o write operation.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 131 figure 5 behavior of the microprocessor interface signals, during an ?intel-type? programmed i/o write operation ale_as a[14:0] cs* d[7:0] wrb_rw data to be written address of target register rdb_ds 1.3.4 p rogrammed i/o a ccess in the m otorola m ode if the xrt94l33 is interfaced to a ?motorola-type? c/ p (e.g., the mc680x0 family, etc.); it should be configured to operate in the ?motorola? mode. moto rola-type programmed i/o ?read? and ?write? operations are described below. 1.3.4.1 t he m otorola m ode r ead c ycle whenever a ?motorola-type? c/ p wishes to read the contents of a r egister or some location within the receive j0 or j1 message buffer, within the xrt94l33 it should do the following. 1. assert the ale_as (address-strobe) input pin by toggling it low. this step enables the address bus input drivers, within the microprocessor interface block of the xrt94l33 ic. 2. place the address of the ?target? register (or buf fer location) within the xrt94l33, on the address bus input pins, a[14:0]. 3. at the same time, the address decoding circuitry (within the user?s system) should assert the cs* (chip select) input pin of the xrt94l33, by toggling it ?low?. this action enables further communication between the c/ p and the xrt94l33 microprocessor interface block. 4. after allowing the data on the address bus pins to settle (by waiting the appropriate ?address setup? time), the c/ p should toggle the ale_as input pin ?high?. this step causes the xrt94l33 to latch the contents of the ?address bus? into its internal circuitr y. at this point, the address of the register or buffer location within the xrt94l33 has now been selected. 5. further, the c/ p should indicate that this cycle is a ?rea d? cycle by setting the wrb_rw (r/w*) input pin ?high?. 6. next the c/ p should initiate the current bus cycle by togglin g the rdb_ds (data strobe) input pin ?low?. this step enables the bi-directional data bus output dr ivers, within the xrt94l33 uni device. at this point, the bi-directional data bus outpu t drivers will proceed to driver the contents of the ?a ddress? register onto the bi-directional data bus, d[7:0]. after some settling time, the data on the ?bi-direct ional? data bus will stabilize and can be read by the c/ p. the xrt94l33 uni will indicate that this data can be read by asserting the rdy_dtck (dtack) signal. after the c/ p detects the rdy_dtck signal (from the xrt9 4l33 uni) it will terminate the read cycle by toggling the ?rdb_ds? (data strobe) input pin ?high?. figure 6 presents a timing diagram which illustrates t he behavior of the micropro cessor interface signals during a ?motorola-type? programmed i/o read operation.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 132 figure 6 illustration of the behavior of micropro cessor interface signals, during a ?motorola-type? programmed i/o read operation ale_as rdb_ds a[14:0] cs* d[7:0] rdy_dtck not valid valid data address of target register wrb_rw
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 133 1.3.4.2 t he m otorola m ode w rite c ycle whenever a motorola-type c/ p wishes to write a byte or word of data into a register or buffer location, within the uni, it should do the following. 1. assert the ale_as (address select) input pin by togg ling it ?low?. this step enables the ?address bus? input drivers (within the uni chip). 2. place the address of the ?target? re gister or buffer location (within the uni), on the address bus input pins, a[14:0]. 3. while the c/ p is placing this address value onto the ad dress bus, the address-decoding circuitry (within the user?s system) should assert the cs* (chip select) input pins of the uni by toggling it ?low?. this step enables further communication between the c/ p and the uni microproces sor interface block. 4. after allowing the data on the address bus pins to settle (by waiting the appropriate ?address setup? time), the c/ p should toggle the ale_as input pin ?high?. this st ep causes the uni device to ?latch? the contents of the ?address bus? into its own circuitry. at this po int, the address of the register or buffer location (within the uni), has now been selected. 5. further, the c/ p should indicate that this current bus cy cle is a ?write? operation by toggling the wrb_rw (r/w*) input pin ?low?. 6. the c/ p should then place the byte or word that it int ends to write into the ?target? register, on the bi- directional data bus, d[15:0]. 7. next, the c/ p should initiate the bus cycle by toggling the rdb_ds (data strobe) input pin ?low?. when the xrt94l33 senses that the wrb_rw (r/w*) input pi n is ?high? and that the rdb_ds (data strobe) input pin has toggled ?low?, it will enable the ?input dr ivers? of the bidirectional data bus, d[7:0]. 8. after waiting the appropriate time, for this newly placed data to settle on the bi-directional data bus (e.g., the ?data setup? time) the uni will as sert the rdy_dtck output signal. 9. after the c/ p detects the rdy_dtck signal (from the uni), the c/ p should toggle the rdb_ds input pin ?high?. this action accomplishes two things. a. it latches the contents of the bi-directional data bus into the xrt94l33 microprocessor interface block. b. it terminates the ?write? cycle. figure 7 presents a timing diagram which illustrates the behavior of the mi croprocessor inte rface signals, during a ?motorola-type? programmed i/o write operation.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 134 figure 7 illustration of the behavior of the microprocessor interface signal, during a ?motorola-type? programmed i/o write operation ale_as a[14:0] cs* d[7:0] rdb_ds rdy_dtck data to be written address of target register wrb_rw 1.4 interrupt struct ure within the xrt 94l33 atm uni/ppp ic the xrt94l33 is equipped with a sophisticated interrupt servicing structure. this interrupt structure includes an interrupt request output pin, (int*), numer ous interrupt enable registers and numerous interrupt status registers. the interrupt se rvicing structure, within the xrt94l33 ic contains three levels of hierarchy. the top level is at the ?operational block level?. the second level is at the ?functional block? level (e.g., the operation control block, receive atm cell processor block, receive ppp processor block, the receive sts-3 toh processor block, the receive sts-3c/sonet poh processor block). the lower hierarchical level is at the individual interrupt or ?source? level. each hierarchical level consists of a complete set of interrupt status registers/bits and interru pt enable registers/bits, as will be discussed below. most of the functional blocks within the xrt94l33 are capable of generating interrupt requests to the c/ p. the xrt94l33 interrupt structure has been carefully des igned to allow the user to quickly determine the exact source of the interrupt (with a minimum number of read operations, and, in-tur n, minimal latency) which will aid the c/ p in determining the appropriate interrupt service r outine to call up in order to either eliminate, or properly respond to the cond ition(s) causing the interrupt. table 6 lists all of the possible conditions that ca n generate interrupts in each functional block of the xrt94l33.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 135 table 6 list of all of the possible conditions that can generate interrupts within the xrt94l33 atm uni/ppp device functional block interrupt condition operation control block ? sts-3 telecom bus ? detection of parity error receive sts-3 toh processor block ? change in the los (loss of signal) defect condition ? change in the lof (loss of frame) defect condition ? change in the sef (severely erred frame) defect condition ? change in the ais-l (line ais) defect condition ? change in the rdi-l (line remote defect indicator) condition ? change in the sd (signal degrade) defect condition ? change in the sf (signal failure) defect condition ? detection of rei-l (line remote error indicator) defect condition ? detection of b1 byte error ? detection of b2 byte error ? detection of new s1 byte ? change in s1 byte unstable condition ? change in j0 (section trace) message unstable condition ? detection of new j0 (section trace) message ? change in j0 ? section trace message mismatch condition ? toh (buffer) capture complete ? change in k1, k2 byte unstable condition ? detection of new k1, k2 byte receive sts-3c/sonet poh processor block ? detection of b3 byte error ? detection of new pointer ? detection of an unknown pointer ? detection of pointer decrement event ? detection of pointer increment event ? detection of ndf pointer ? change in the loss of pointer (lop-p) defect condition ? change in the ais-p (path ? ais) defect condition ? detection of new j1 (path trace) message ? detection of rei-p (path remote error in dicator) event ? change in the uneq-p defect condition ? change in the plm-p defect condition ? detection of new c2 byte value
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 136 ? change of ?c2 byte? unstable condition ? change in the tim-p defect condition ? change of rdi-p (path remote defect indicator) condition ? change in the ?rdi-p unstable? condition ? change in ais-c (ais concatenation) condition ? change in lop-c (lop concatenation) condition receive atm cell processor block ? receive cell extraction event ? receive cell insertion event ? receive cell insertion memory overflow condition ? receive cell extraction memory overflow condition ? rxfifo overflow ? detection of correctable hec byte error ? detection of uncorrectable hec byte error ? change of lcd (loss of cell delineation) condition ? change of ocd (out of cell delineation) condition transmit atm cell processor block ? transmit cell extraction event ? transmit cell insertion event ? transmit cell insertion memory overflow condition ? transmit cell extraction memory overflow condition ? txfifo overflow ? detection of hec byte error ? detection of transmit utopia parity error receive ppp processor block ? detection of receive fifo overflow condition ? detection of fcs (fra me check sequence) error ? detection of abort sequence ? detection of runt packet transmit ppp processor block ? detection of transmit fifo underflow condition ? detection of parity error the xrt94l33 atm uni/ppp comes equipped with the followi ng registers to support the servicing of this wide array of potential ?inte rrupt request? sources.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 137 table 7 a listing of the xrt94l33 atm uni/ppp device interrupt block registers r egister a ddress l ocation operation interrupt status register ? byte 0 0x010b operation interrupt enable register ? byte 0 0x010f operation block interrupt stat us register ? byte 1 0x0112 operation block interrupt stat us register ? byte 0 0x0113 operation block interrupt enable register ? byte 1 0x0116 operation block interrupt enable register ? byte 0 0x0117 receive sts-3 transport interrupt st atus register ? byte 2 0x1109 receive sts-3 transport interrupt st atus register ? byte 1 0x110a receive sts-3 transport interrupt st atus register ? byte 0 0x110b receive sts-3 transport interrupt enable register ? byte 2 0x110d receive sts-3 transport interrupt enable register ? byte 1 0x110e receive sts-3 transport interrupt enable register ? byte 0 0x110f receive sts-3c path ? interrupt status register ? byte 2 0x1189 receive sts-3c path ? interrupt status register ? byte 1 0x118a receive sts-3c path ? interrupt status register ? byte 0 0x118b receive sts-3c path ? interrupt enable register ? byte 2 0x118d receive sts-3c path ? interrupt enable register ? byte 1 0x118e receive sts-3c path ? interrupt enable register ? byte 0 0x118f redundant receive sts-3 transport interr upt status register ? byte 2 0x1709 redundant receive sts-3 transport interr upt status register ? byte 1 0x170a redundant receive sts-3 transport interr upt status register ? byte 0 0x170b redundant receive sts-3 transport interr upt enable register ? byte 2 0x170d redundant receive sts-3 transport interr upt enable register ? byte 1 0x170e redundant receive sts-3 transport interr upt enable register ? byte 0 0x170f receive sonet poh interrupt status r egister ? byte 2 ? channel n-1 0xn189 receive sonet poh interrupt status regi ster ? byte 1 ? channel n-1 0xn18a receive sonet poh interrupt status regi ster ? byte 0 ? channel n-1 0xn18b receive sonet poh - path interrupt enable register ? byte 2 ? channel n-1 0xn18d receive sonet poh - path interrupt enable register ? byte 1 ? channel n-1 0xn18e
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 138 table 8 a listing of the xrt94l33 atm uni/ppp device interrupt block registers r egister a ddress l ocation receive sonet poh - path interrupt enable register ? byte 0 ? channel n-1 0xn18f ds3/e3 framer block ? block interrupt enable register ? channel n-1 0xn304 ds3/e3 framer block ? block interrupt status register ? channel n-1 0xn305 ds3/e3 framer block ? rxds3/e3 interrupt enable register ? channel n-1 0xn312 ds3/e3 framer block ? rxds3 interr upt status register ? channel n-1 ds3/e3 framer block ? rxe3 interrupt enable register # 2 ? channel n-1 0xn313 ds3/e3 framer block ? rxe3 interrupt st atus register # 1 ? channel n-1 0xn314 ds3/e3 framer block ? rxe3 interrupt st atus register # 2 ? channel n-1 0xn315 ds3/e3 framer block ?rxds3 feac interrupt enable/status register ? channel n-1 0xn317 ds3/e3 framer block ? receive plcp interrupt enable register ? channel n-1 0xn391 ds3/e3 framer block ? receive plcp interr upt status register ? channel n-1 0xn392 receive atm interrupt status regist er ? byte 1 ? channel n-1 0xn70a receive atm interrupt status register ? byte 0 ? channel n-1 receive ppp interrupt status register ? channel n-1 0xn70b receive atm interrupt enable register ? byte 1 ? channel n-1 0xn70e receive atm interrupt enable register ? byte 0 ? channel n-1 receive ppp interrupt enable register ? channel n-1 0xn70f receive mapper interrupt status register ? byte 0 ? channel n-1 0xnb0b receive mapper interrupt enable register ? byte 0 ? channel n-1 0xnb0f transmit atm interrupt status register ? channel n-1 transmit ppp interrupt status register ? channel n-1 0xnf0b transmit atm interrupt enable register ? channel n-1 transmit ppp interrupt enable register- channel n-1 0xnf0f note: in table _, the value of n ranges from 1 (which corresponds with channel 0) to 3 (which corresponding with channel 2).
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 139 1.4.1 g eneral f low of xrt94l33 atm uni/ppp d evice i nterrupt s ervicing when any of the conditions, presented in figure 6 occu rs (if their interrupt is enabled), then the xrt94l33 will generate an interrupt request to the p/ c by asserting the active-low inte rrupt request output pin, int*. shortly after the p/ c has detected the activated int* signal, it w ill enter into the appropriate ?user-supplied? interrupt service routine. the first task, for the p/ c, while running this interrup t service routine, may be to isolate the source of the interrupt request down to the device level (e.g., the xrt94l33 atm uni/ppp device), if multiple peripheral devices exist in the user?s system. however, once the ?interrupting peripheral? device has been identified and determined to be the xrt94l33, the next task for the p/ c is to identify the functional block with in the xrt94l33 requested the interrupt. finally, the p/ c will need to proceed further and identify the ex act condition(s) causing the interrupt to be generated by the xrt94l33. the procedure for servicing the ?xrt94l33? interrupts is best achieved by exec uting the following steps. step 1 ? determine the functional block(s) requesting the interrupt if the interrupting device turns out to be the xrt94l33 atm uni/ppp ic, then the c/ p must determine which ?functional block? requested the interrupt. hence, upon reaching this state, one of the very first things that the c/ p must do within the user supplied ?xrt94l33? inte rrupt service routine, is to perform a read of both of the following registers. ? operation block interrupt status register ? byte 1 (address = 0x0112) ? operation block interrupt status register ? byte 0 (address = 0x0113) the bit-format of each of thes e registers is presented below. operation block interrupt status register ? byte 1 (address location = 0x0112) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 op control block interrupt status ds3/e3 mapper block interrupt status unused receive sts-1 toh processor block interrupt status receive sts-1 poh processor block interrupt status ds3/e3 framer block interrupt status receive line interface block interrupt status unused r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 operation block interrupt status register ? byte 0 (address location = 0x0113) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive atm cell processor block interrupt status receive sts-3 toh processor block interrupt status receive sonet/ sts-3c poh processor block interrupt status receive ppp processor block interrupt status transmit atm cell processor block interrupt status unused transmit ppp processor block interrupt status r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 140 each of the ?operation block interrupt status? regi sters presents the ?interrupt -request? status of each functional block, within the chip. the pur pose of these two registers is to help the c/ p identify which functional block(s) has requested the interrupt. whichever bit(s) are asserted, in this register, identifies which block(s) have experienced an ?inter rupt-generating? condition as pres ented in table _. once the c/ p has read this register, it can determine which ?branch? within the interrupt service routi ne that it must follow in order to properly service this interrupt. the xrt94l33 atm uni/ppp ic further supports the operat ional block hierarchy by providing the operation block interrupt enable register ? bytes 1 and 0. the bit format of these two registers are identical to that for the operation block interrupt status registers ? bytes 1 and 0, and are presented below for the sake of completeness. operation block interrupt enable register ? byte 1 (address location = 0x0116) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 op control block interrupt enable ds3/e3 mapper block interrupt enable unused receive sts-1 toh processor block interrupt enable receive sts-1 poh processor block interrupt enable ds3/e3 framer block interrupt enable receive line interface block interrupt enable unused r/w r/w r/w r/w r/w r/w r/w r/o 0 0 0 0 0 0 0 0 operation block interrupt enable register ? byte 0 (address location = 0x0117) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive atm cell processor block interrupt enable receive sts-3 toh processor block interrupt enable receive sonet/ sts-3c poh processor block interrupt enable receive ppp processor block interrupt enable transmit atm cell processor block interrupt enable unused transmit ppp processor block interrupt enable r/w r/w r/w r/w r/w r/o r/o r/w 0 0 0 0 0 0 0 0 these operation block interrupt enable registers permit the user to indivi dually enable or disable the interrupt requesting capability of the functional bl ocks within the xrt94l33. if a particu lar bit-field, within this register contains the value ?0?, then the corresponding functi onal block has been disabled for generating any interrupt requests. conversely, if that bit-field contains the va lue ?1?; then the corresponding functional block has been enabled for interrupt generation (e.g., those potential interrupt s, within the ?enabled functional block? that are enabled at the source level are now enabled). the us er should be aware of the fact that each functional block, within the xrt94l33 contains multiple potential interrupt sources. each of these lower level interrupt sources contain their own set of interrupt enable bits and interrupt status bits, existing in various on-chip registers.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 141 step 2 ? interrupt service routing branching: after reading the operation block interrupt status registers the contents of the operation block interrupt status register s permit the user to identify which of the seven (7) functional blocks (within the xrt94l33 ic) have requested interrupt service. the p/ c should use this information in order to determine where, within the in terrupt service routine, pr ogram control should branch to. the following table can be viewed as an ?interrupt se rvice routine? guide. it li sts each of the functional blocks that contain bit-field in the operation block in terrupt status and enable regi sters. additionally, this table also presents a list and addresses of the corres ponding on-chip registers t hat the interrupt service routine should branch to and read; bas ed upon the interrupt functional block. table 9 interrupt service routine guide for the xrt94l33 i nterrupting f unctional b lock t he n ext r egister to be r ead d uring the i nterrupt s ervice r outine a ddress l ocation operation control block operation interr upt status register ? byte 0 0x010b receive atm cell processor block operation channel interrupt indicator ? receive atm cell processor block 0x0128 receive sonet/sts-3c poh processor block operation channel interrupt indicator ? receive sonet poh processor block 0x0120 receive sts-3 transport interrupt st atus register ? byte 2 0x1109 receive sts-3 transport interrupt st atus register ? byte 1 0x110a receive sts-3 toh processor block receive sts-3 transport interrupt st atus register ? byte 0 0x110b receive ppp packet processor block operation channel interrupt indicator ? receive ppp packet processor block 0x012a transmit atm cell processor block operation channel interrupt indicator ? transmit atm cell processor block 0x0127 transmit ppp packet processor block operation channel interrupt indicator ? transmit ppp packet processor block 0x0129 ds3/e3 mapper block operation channel interrupt indicator ? ds3/e3 mapper block 0x0126 ds3/e3 framer block operation channel interrupt indicator ? ds3/e3 framer block 0x0122 note: registers associated within each functional block are specified in ascending order (based upon the on-chip address location). no other inferences should be m ade regarding the order in which these registers are presented in this table. once the c/ p has read out the contents of the appropriate register (as listed above in table 9); then there may (or may not) be additional ?interrupt stat us? registers to read; as described below. interrupt servicing for the ?operation control? block if the interrupt service routine is currently servicing an ?operation control? block interrupt, then reading out the contents of the corresponding r egister (as presented in table 9) should result in the following occurrences. 1. the c/ p will uniquely identify the source or condition causing the interrupt request. 2. the ?asserted interrupt stat us? bit-fields within this re gister will be reset upon read. 3. the ?asserted? bit-field(s), within the operation block interru pt status register will be reset.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 142 4. the xrt94l33 will negate the ?int*? (interrupt request) output pin. once these events have occurred, then (as far as the xrt94l33 is concerned) the interrupt has been serviced. 1.4.1.1 i nterrupt s ervicing for the ?r eceive sts-3 toh p rocessor ? b lock if the interrupt service routine is currently servicing an ?receive sts-3 toh processor? block interrupt, then reading out the contents of the corresponding register (as presented in table _) should result in the following occurrences. 1. the c/ p will uniquely identify the source or condition causing the interrupt request. 2. the ?asserted interrupt status? bit-fields within these registers will be reset upon read. 3. the ?asserted? bit-field(s), within the operation block interru pt status register will be reset. 4. the xrt94l33 will negate the ?int*? (interrupt request) output pin. once these events have occurred, then (as far as the xrt94l33 is concerned) the interrupt has been serviced. the remainder of the user?s interrupt service routine sh ould now execute the appropriate steps to respond to the conditions causing this interrupt request. 1.4.1.2 i nterrupt s ervicing for the remaining blocks within the xrt94l33 if the interrupt service routine is currently servic ing interrupts associated with the following blocks. ? receive atm cell processor block ? receive ppp packet processor block ? receive sts-3c/sonet poh processor block ? transmit atm cell processor block ? transmit ppp packet processor block ? ds3/e3 mapper block ? ds3/e3 framer block then there are still more steps that the p/ c must take in order to fully service these interrupts. step 3 ? identify the interrupting channel for each of the ?above-mentioned? blocks, the user wa s advised (in table 9) to read out the contents of a ?channel interrupt indicator? register. this regist er will uniquely identify the ?interrupting? channel. for example, the bit-format of t he ?operation channel interrupt indicator ? receive sts-3c/sonet poh processor block? register is presented below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 143 operation channel interrupt indicator ? receive sts-3c/sonet poh processor block (address = 0x0120) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused receive sts- 3c poh processor block ? channel interrupt indication status unused receive sonet poh processor block - channel 2 interrupt indication status receive sonet poh processor block - channel 1 interrupt indication status receive sonet poh processor block - channel 0 interrupt indication status r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 if a given bit-field is set to ?1?, then the ?recei ve sts-3c/sonet poh processor? block, (within the corresponding channel) is generating an interrupt request. conversely, if a given bit-field is set to ?0?, then the ?receive sts-3c/sonet poh proc essor? blocks (within the correspondi ng channel) is no t generating an interrupt request. the ?operation channel interrupt indica tor? registers for the othe r functional blocks are virtually identical to that presented for the ?receive st s-3c/sonet poh processor? block. step 4 ? proceed to read out the appropriate ?sourc e-level? interrupt status registers; corresponding to the ?interrupt ing? channel. now that the ?interrupting? functional block and chann el has been identified, the p/ c should now go off and read out the contents of the appropriate ?sou rce-level? interrupt status register. table 10 presents a list of ?functional blocks? and the corresponding ?source-level? interrupt status registers that the c/ p should read, once the ?interrupting? channel (n) has been identified.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 144 table 10 list of ?source-level? interrupt status re gisters that should be read, once ?interrupting? channel has been identified i nterrupting f unctional b lock t he n ext r egister to be read during the i nterrupt s ervice r outing a ddress l ocation receive atm interrupt status regist er ? byte 1 ? channel n-1 0xn70a receive atm cell processor block receive atm interrupt status regist er ? byte 0 ? channel n-1 0xn70b receive ppp packet processor block receive ppp interrupt status r egister ? channel n-1 0xn70b receive sonet poh interrupt status r egister ? byte 2 ? channel n-1 0xn189 receive sonet poh interrupt status regi ster ? byte 1 ? channel n-1 0xn18a receive sonet poh processor block receive sonet poh interrupt status regi ster ? byte 0 ? channel n-1 0xn18b receive sts-3c path interrupt status register ? byte 2 0x1189 receive sts-3c path interrupt status register ? byte 1 0x118a receive sts-3c poh processor block receive sts-3c path interrupt status register ? byte 0 0x118b transmit atm cell processor block transmit atm interrupt status r egister ? channel n-1 0xnf0b note: the value ?n? (within the address locations of these register s) ranges in value from 1 to 3, and corresponding to ?interrupting? channel n-1.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 145 1.5 an overview of possible configuration options in the xrt94l33 the xrt94l33 can be configured to function a wide va riety of operating modes. this section briefly summarizes and describes the procedure that one should employ in order to configure the xrt94l33 into each of these modes. in all, the xrt94l33 can be configured to function in any of the following modes. ? 1 channel sts-3c and up to 2 channel ds3/e3 atm uni/ppp mode ? 1-channel sts-3 (e.g., 3 channels of atm uni/ppp over sts-1, which is in-turn is mapped into sts-3) mode ? 1-channel sts-3 (e.g., 3 channels of atm uni/ppp over ds3/e3, which is in-turn, mapped into sts-3) mode each of these operating modes is described below. 1.5.1 1-c hannel sts-3 c and up to 2 c hannels ds3/e3 atm uni/ppp m ode if the user configures the xrt94l33 to operate in th is mode, then the xrt94l33 will function as an atm uni/ppp device that supports atm ce ll or ppp packet transmission and re ception over one sts-3c channel and possibly as many as two additional ds3/e3 chann els, in parallel. since the utopia and pos-phy interfaces, within the xrt94l33 support multi-phy oper ation, the atm layer processor will have no problem writing atm cell/ppp packet data into and reading at m cell/ppp packet data from the utopia/pos-phy interface. figure 8 presents the functional block diagram of the xrt94l33, if it is configured to operate in this mode. transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3 toh processor block receive sts-3 toh processor block transmit sts-3 toh processor block transmit sts-3 toh processor block receive sts-3c poh processor block receive sts-3c poh processor block transmit sts-3c poh processor block transmit sts-3c poh processor block sts-3 telecom bus interface block sts-3 telecom bus interface block sts-3 pecl interface block sts-3 pecl interface block sts-3 cdr block sts-3 cdr block xrt94l33 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block some notes about the above figure figure 8 indicates that the xrt94l33 is functioning as a 1-channel sts-3c atm uni/ppp device. the existence of the two ds3/e3 channels are not depicted in this illustration. nonetheless, whenever the xrt94l33 is operating in this mode, these additional ds 3/e3 channels are available for the transmission of atm cell or ppp packet.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 146 configuring the xrt94l33 to operate in the ?1-channel sts-3c (with 0 to 2-channel ds3/e3) atm uni/ppp mode. to configure the xrt94l33 to operate in th is mode execute the following two steps. step 1 - set bits 1 and 0 (conf[1:0]), within the operation control register ? byte 3; to [0, 1]; as depicted below. operation control register ? byte 3 (address = 0x0100) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 ch_mode_sel[3:0] dual bus unused conf[1:0] r/w r/w r/w r/w r/w r/o r/w r/w x x x x x 0 0 0 step 2 ? set bit 2 (ppp/atm*), within the ?o peration control regist er- byte 0? to the appropriate value as depicted below. operation control register ? byte 0 (address = 0x0103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit utopia pll off receive utopia pll off unused ppp/atm* unused sw reset r/w r/w r/o r/o r/o r/w r/o r/w 0 0 0 0 0 x 0 0 setting this bit-field to ?0? configures the xrt94l33 to operate in the atm uni mode. conversely, setting this bit-field to ?1? configures the xrt94l33 to operate in the ppp mode. please refer to section 4.0 for a description on how to configure the xrt94l33 to operate in the atm uni mode. further, please refer to section 5.0 for a desc ription on how to configure the xrt94l33 to operate in the ppp mode. 1.5.2 1-c hannel sts-3 atm uni/ppp m ode if the user configures the xrt94l33 to operate in this mode, then the xrt94l33 will function as a 1-channel sts-3 atm uni/ppp device.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 147 figure 9 presents the functional block diagram of the xrt9 4l33, if it is configured to operate in this mode.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 148 figure 9 illustration of the xrt94l33, when it is c onfigured to operate in the 1-channel sts-3 atm uni/ppp mode transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3 toh processor block receive sts-3 toh processor block transmit sts-3 toh processor block transmit sts-3 toh processor block receive sonet poh processor block receive sonet poh processor block transmit sonet poh processor block transmit sonet poh processor block sts-3/12 telecom bus interface block sts-3/12 telecom bus interface block sts-3/12 pecl interface block sts-3/12 pecl interface block sts-3/12 cdr block sts-3/12 cdr block xrt94l33 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block from channels 1 and 2 to channels 1 and 2 configuring the xrt94l33 to operate in the ?1-channel sts-3 atm uni/ppp mode to configure the xrt94l33 to operate in this mode execute the following steps. step 1 ? set bits 1 and 0 (conf[ 1:0]), within the operation control register ? byte 3; to [1, 1]; as depicted below. operation control register ? byte 3 (address = 0x0100) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 ch_mode_sel[3:0] dual bus unused conf[1:0] r/w r/w r/w r/w r/w r/o r/w r/w x x x x x 0 1 1 step 2 ? set bit 2 (ppp/atm*), within the ?o peration control regist er- byte 0? to the appropriate value as depicted below. operation control register ? byte 0 (address = 0x0103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit utopia pll off receive utopia pll off unused ppp/atm* unused sw reset r/w r/w r/o r/o r/o r/w r/o r/w 0 0 0 0 0 x 0 0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 149 setting this bit-field to ?0? configures the xrt94l33 to operate in the atm uni mode. conversely, setting this bit-field to ?1? configures the xrt94l33 to operate in the ppp mode. please refer to section 4.0 for a description on how to configure the xrt94l33 to operate in the atm uni mode. further, please refer to section 5.0 for a desc ription on how to configure the xrt94l33 to operate in the ppp mode. 2.0 atm uni mode operation if the xrt94l33 (or a given channel within the xrt94l3 3) has been configured to operate in the atm uni mode, then the following functional blocks will become active. ? the transmit utopia interface block ? the transmit atm cell processor block ? the transmit sts-3c/sonet poh processor block ? the transmit sts-3 toh processor block ? the receive sts-3 toh processor block ? the receive sts-3c/sonet poh processor block ? the receive atm cell processor block ? the receive utopia interface block each of these functional blocks will be discussed in considerable detail, over the next few sections. 2.1 configuring the xrt94l33 to operate in the atm uni mode the user can configure a given channel within the xr t94l33 to operate in the atm uni mode by setting bit 2 (ppp/atm*) within the operation control regist er ? byte 0; to ?0? as depicted below. operation control register ? byte 0 (address = 0x0103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 tx utopia clock de- skew pll off rx utopia clock de- skew pll off transmit sts-3 resync reserved ppp/ atm* reserved software reset r/w r/w r/w r/o r/o r/w r/w r/w 0 0 0 0 0 0 0 0 once the user executes this step, then the entire xrt94l33 will be configured to operate in the atm uni mode.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 150 2.2 the transmit direction if a given channel (or the entire device) is configured to operate in the atm mode, then the purpose of the transmit section within the xrt94l33 1-channel sts- 3c/sts-3 atm uni device is to allow a local atm layer (or atm adaptation layer) processor to transmit atm cell data to a remote piece of equipment via an oc-3c or oc-3 transport medium for atm uni applications, the transmit section of t he xrt94l33 chip consists of the following functional blocks: ? transmit utopia interface block ? transmit atm cell processor block ? transmit sts-3c poh processor bl ock (for sts-3c applications) ? transmit sonet poh processor bl ock (for sts-3 applications) ? transmit sts-3 toh processor block the atm layer processor will write atm cell data to t he transmit utopia interfac e block of the xrt94l33. the transmit utopia interface block provides the i ndustry standard atm/phy interface functions. the transmit utopia interface block will ultimately write this cell data to an internal fifo (referred to as txfifo throughout this document); where it can be read and fu rther processed by the transmit atm cell processor block. the transmit utopia interface block will also provide signaling to suppor t data-flow control between the atm layer processor and the transm it utopia interface block. the transmit atm cell processor block will read in the at m cell data from the txfi fo. as the transmit atm cell processor block reads in this atm cell data (from the tx fifo) it will perform some parity checking on this data. if the transmit atm cell processor block detects any parity errors in these incoming atm cells, then these atm cells are optionally discarded. afte rwards, all ?error-free? atm cell data will then be processed by a ?user-defined? (e.g., ?transmit user?) ce ll filter. all cells (with header bytes) that do not comply with the ?user-defined? filter ing requirements will be (optionally) disc arded. additionally, this transmit user cell filter can be configured to copy and route ?replicate? cells (that contain ?header-byte? patterns that match the ?user-defined? cell filtering criteria) to the ?transmit cell extraction? bu ffer/processor where these atm cells can be read out and processed via the micropr ocessor interface. continuing along the transmit output path, the transmit atm cell processor block will t hen (optionally) proceed to take the first four octets of a given cell and compute the hec (header error check) byte from these bytes. afterwards the transmit atm cell processor block will insert this hec byte into the 5th octet positi on within the cell. the transmit atm cell processor block will also (optionally) scramble the payload portion of the ce ll (bytes 6 through 53) in order to prevent user data from mimicking framing or control bits/bytes. once the cell has gone through this process it will then be transferred to either of the tr ansmit sts-3c poh processor block or the corresponding transmit sonet poh processor blocks for further processing. if the txfifo (within the transmit utop ia interface block) is depleted and has no (user) cells available, then the transmit atm cell processor block will automatically read out the content s of all cells residing within the ?transmit cell insertion? buffer, and will transmit these cells into the outbound atm cell traffic via the ?transmit data path?. once the ?transmit cell in sertion buffer? has been depleted, then the transmit atm cell processor block will generate, process and transmit idle cells, in the exact same manner as with user cells. this generation and transmission of idle cells is also known as cell-rate decoupling (e.g., idle cells are generated in order to fill up the bandwidth of the pmd carrier requirements ? 155.52 mbps in this case). the transmit atm cell processor block has provisions to allow the user to generate and transmit certain ?user- defined? cells, such as oam cells via the ?transmit cell insertion? processor block. note: these special or oam cells will be subjected to the same processing as are user and idle cells (e.g., hec byte calculation and insertion, cell payload scrambling).
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 151 the transmit sonet poh processor or transmit sts-3c poh processor block will accept these atm cells and will map them into either an sts-1 or sts-3c spe, respectively. additionally, the transmit sonet poh processor block or the transmit sts- 3c poh processor block also has re sponsibility of generating the poh bytes for these spes, prior to routing this data to the transmit sts-3 toh processor block. the transmit sts-3 toh processor block will take the sts-1 spe dat a (from the transmit sonet poh processor block) or the sts-3c spe (from the transmit sts-3c poh proc essor block) and will generate and overhead the toh bytes within each outbound sts-3 frame. the following sections discuss the blocks comprising the transmitter portion of the xrt94l33 in detail. 2.2.1 transmit utopia interface block the transmit utopia input interfac e complies with utopia level 1, 2 and 3 standard interface (e.g., the transmit utopia can support both single-phy and mu lti-phy operations.) additionally, the xrt94l33 provides the user with the option of varying the follow ing features associated with the transmit utopia bus interface. ? operating the transmit utopia data bu s per the utopia levels 1, 2 or 3 standards ? transmit utopia data bus width of 8 or 16 bits ? the cell size (e.g., the number of octets being processed per cell via the utopia bus) ? assigning a utopia address to a given sts-3c port. ? whether the transmit utopia clock de-skewing pll is enabled or not. figure 10 presents a simplistic illustra tion of the transmit utopia interfac e block, along with its external input pins. figure 10 a simple illustration of the transmit utopia interface block to transmit atm cell processor txuclk txudata[15:0] txuprty txusoc txuenb* tfullb*/txucla v txuaddr[4:0] transmit utopia interface block txuclko to transmit atm cell processor txuclk txudata[15:0] txuprty txusoc txuenb* tfullb*/txucla v txuaddr[4:0] transmit utopia interface block txuclko
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 152 2.2.1.1 the pins of the transmit utopia bus interface the atm layer processor will interfac e to the transmit utopia interfac e block via the following pins. ? txudata[15:0] - transmit utopia data bus input pins ? txuaddr[4:0] - transmi t utopia address bus input pins ? txuclk transmit utopia interface block clock input pin ? txuclko transmit utopia interface block clock output pin ? txusoc transmit ?start of cell? indicator input pin ? txuprty transmit utopia - odd parity input pin ? txuenb* transmit utopia data bus - write enable input pin ? txuclav/tfullb* txfifo cell available each of these signals is briefly discussed below. txudata[15:0] - transmit utopia data bus inputs the atm layer processor will write its atm cell data into the transmit utopia interf ace block, by placing it, in a byte-wide (or 16-bit word-wide) manner on these input pins. the transmit utopia data bus can be configured to operate in the ?8-bit wide? or ?16-bit wide? mode (see section _). if the ?8-bit wide? mode is selected, then only the txudata[7:0] input pins are active and capable of accepting atm cell data from the atm layer processor. if the ?16-bit wide? mode is se lected, the all 16 input pins (e.g., txudata[15:0]) are active. the transmit utopia data bus is tri-stated while the active-low txuenb* (transmit utopia data bus - write enable) input signal is ?high?. therefore, the atm layer processor must assert this signal (e.g., toggling txuenb* ?low?) in order write the cell data, on the transmit utopia data bus, into the transmit utopia interface block. the data on the transmit utopia data bus is sampled and latched into the transmit utopia interface block, on the rising edge of the transmit utop ia interface block clock signal, txuclk. additionally, the transmit utopia interface block will only process one cell worth of data (e.g., 52, 53 or 54 bytes, as configured via the cell_size_sel[1:0] option - see section _), following the latest assertion of the txusoc (transmit-start of cell) pin. afterwards, the transmit utopia data bus will become tri-stated and will cease to process any more data from the atm laye r processor until the next assertion of the txusoc pin. once the transmit utopia interface block reache s this condition, it will ignore the assertions of the txuenb* pin, and will keep the transmit utopia data bus input pins tri-stated until the atm layer processor pulses the txusoc input pin, once again. if the transmit utopia interface block detects a ?runt? cell (e.g., if the amount of data that is read into the txufifo is less than that configured via the ?cell_siz e_sel[1:0]? option), then the transmit utopia interface block will discard this cell, and resume normal operation. txuaddr[4:0] - transmit utopia address bus inputs these input pins are only used when the xrt94l33 is oper ating in the multi-phy mode. therefore, for more information on the transmit utopia a ddress bus, please see section _. txuclk - transmit utopia interface block - clock signal input pin the transmit utopia interface block uses this signal to sample and latch the data on the transmit utopia data bus into the transmit utopia address block (for multi-phy operation) into the transmit utopia interface block. this clock signal can run at frequencies of up to 50 mhz.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 153 txuclko ? transmit utopia interface block clock output signal if the ?transmit utopia clock de-skewing? pll is enabled, then the atm layer processor can use this signal to clock out the contents of the ?outbound? atm cells, and to assert the ut opia address (during multi- phy operation). similar to the ?txuclk? signal, this signal can run at frequencies up to 50mhz. txuenb* - transmit utopia data bus - write enable input the transmit utopia data bus is tri-stated while this input signal is negated. therefore, the atm layer processor must assert this ?active-lo w? signal (toggle it ?low?) in order to write the byte (or word) on the transmit utopia data bus, into the transmit utopia interface block. txuprty - transmit utopia - odd parity bit input pin the atm layer processor is expected to compute the odd-parity value of each byte (or word) of atm cell data that it intends to place on the transmit utopia da ta bus. the atm layer processor is then expected to apply this parity value at the txuprty pin, while the corresponding byte (or word) is present on the transmit utopia data bus. this signal, along with the corres ponding byte (or word) of atm cell data will be routed to the transmit atm cell processor block fo r ?transmit utopia parity verification?. txusoc - transmit utopia - ?start of cell? indicator the atm layer processor is expected to pulse this i nput signal ?high?, for one clock period of txuclk, when the first byte (or word) of a given atm cell is present on the transmit utopia data bus. this signal must be kept ?low? at all other times. note: once the atm layer processor has pulsed the txusoc pin ?high?, the transmit utopia interface block will proceed to read in and process only one cell of data (e.g., 52, 53, or 54 bytes, as configured via the ?cell_size_sel[1:0]? option - see section _) via the tr ansmit utopia data bus. afterwards, the transmit utopia interface block will cease to process any more data from the atm layer processor until the txusoc pin has been pulsed ?high? once again. this phenomenon is more clearly defined in ?example - 1? below. example -1 for example, if the user c onfigures the transmit utopia interface block to process 53 bytes per cell; then following the assertion of the txusoc pin (which is coin cident with the placement of the first byte of the cell on the transmit utopia data bus), the transmit utopia interface block will read in and process 52 more bytes of data via the transmit utopia data bus resulti ng in a total of 53 bytes being processed. after the transmit utopia interface block has read in the 53rd byte, it will no longer read in any more data from the atm layer processor, (even if t he ?txuenb*? input pin is pulled ?low?) until the txusoc pin has been asserted. txuclav/tfullb* - tx fifo cell available/txfifo full* this output signal is used to provide some data flow control between the atm layer processor and the transmit utopia interface block. please see section _ for more information regarding this signal. 2.2.1.2 c onfiguration o ptions with the t ransmit utopia i nterface block s electing the utopia l evel the xrt94l33 permits the user to configure the transmit utopia interface block in either of the following ?utopia levels?. ? utopia level 3 ? utopia level 1 or 2 the user can configure the transmit utopia inte rface block within the xrt94l33 to operate in the appropriate utopia level, by writing the appropriate value into bit 7 (utopia level) within the ?transmit utopia control register?, as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 154 transmit utopia control register ? byte 0, address = 0x0583 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level 3 disable multi-phy mode back-to- back polling enable direct status access transmit utopia/pos- phy data bus width[1:0] cell_size_sel[1:0] r/w r/w r/w r/w r/w r/w r/w r/w x 0 0 0 x x 1 1 setting this bit-field to ?0? configures the transmit utopia interface block to support ?utopia level 3? signaling. conversely, setting this bit-field to ?1? co nfigures the transmit utopia interface block to support the ?utopia levels 1 and 2? form of signaling. a description of the operation of the transmit utopia interface block, for utopia level 1, 2 and 3 operation is presented below. 2.2.1.3 utopia l evel 1 and 2 o peration of the t ransmit utopia i nterface b lock this section presents an in-depth write up of the utopia level 1 and 2 protocols. when the transmit utopia interface block has been co nfigured to operate in the ?utopia level 2? mode, then it will either be configured to operate in the ?s ingle-phy? or ?multi-phy? mode, as described below. 2.2.1.3.1 selecting the utopia data bus width the user can configure the width of the transmit utopia data bus to be either 8 or 16 bits by writing the appropriate data into bits 3 and 2 (transmit utopia data bus width[1:0]) within the ?transmit utopia control? register, as depicted below. transmit utopia control register ? byte 0, address = 0x0583 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level multi-phy mode back-to- back polling enable direct status access transmit utopia data bus width[1:0] cell_size_sel[1:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 0 0 0 x x 1 1 if the user chooses a utopia data bus width of 8 bits, then only the transmit utopia data inputs: txudata[15:8] will be active. (the input pins: txudata[7:0] will not be active ). if the user chooses a utopia data bus width of 16 bits, then all of the transmit utopia data inputs: txudata[15:0] will be active. the following table relates the value of bits 2 and 3 (trans mit utopia data bus width[1:0]) within the transmit utopia control register, to the corresponding width of the transmit utopia data bus. note: this configuration setting does not apply to the receive utopia interface block. the user will still need to specify the width of the receive utopia data bus, separately, as described in section _.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 155 table 11 the relationship between the contents of ?transmit utopia data bus width[1:0] within the transmit utopia control register and the operating width of the transmit utopia data bus t ransmit utopia d ata b us w idth [1:0] w idth of t ransmit utopia d ata b us 00 in-active: 01 8 bits 10 16 bits 11 not valid (do not use) 2.2.1.3.2 selecting the cell size (number of octets per cell) the xrt94l33 permits the user to select the number of octets per cell that the transmit utopia interface block will process, following each assertion of the txusoc input pin. specifically, the user has the following cell size options. ? if the utopia data bus width is set to 8 bits then the user can choose: 52 bytes (with no hec byte in the cell), or 53 bytes (with either a dummy or actual hec byte in the cell) ? if the utopia data bus width is set to 16 bits then the user can choose: 52 bytes (with no hec byte in the cell), or 54 bytes (with either a dummy or actual hec byte, and a stuff byte in the cell) the user makes his/her selection by writing the appropriate data into bits 1 and 0 (cell_size_sel[1:0]) within the transmit utopia control re gister, as depicted below. transmit utopia control register ? byte 0, address = 0x0583 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level multi-phy mode back-to- back polling enable direct status access transmit utopia data bus width[1:0] cell_size_sel[1:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 0 0 0 1 1 x x the following table presents the relationship between t he value of these bits and the number of octets/cell that the transmit utopia in terface block will process.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 156 table 12 the relationship between the contents of bits 1 and 0 (cell_size_sel[1:0]) within the transmit utopia control register, and the number of octets per cell that will be processed by the transmit utopia interface blocks per assertion of txusoc c ell _s ize _s el [1:0] n umber of b ytes /c ells 00 52 bytes/cell 01 53 bytes/cell (only valid if the transmit utopia data bus width = 8 bits) 10 54 bytes/cell 11 unused once the user has implemented his/her selection for t he cell size, then the transmit utopia interface block will be configured to accept the ?cell size? number of oc tets, per each assertion of the ?txusoc? input pin. once the transmit utopia interface block has accepted ?cell size? number of byte s then it will not accept any more octets until the ?txusoc? in put pin has been pulsed ?high? again. note: in this case the transmit utopia interface block will ce ase accepting more octets, even if the ?txuenb* input pin is pulled ?low?. these additional bytes are simply ignored by the ?transmit utopia interface? block. 2.2.1.3.3 cell-level handshaking atm forum documentation refers to both ?cell level ? and ?octet-level? handshaking. however, the xrt94l33 only supports the ?cell-level? handshaking mode . octet-level handshaking is not supported. in the ?cell-level? handshaking mode, when the xrt94l33 sets the txuclav output pin to a logic ?1?, it means that the tx fifo has enough remaining empty space for it to receive at least one more full cell of data from the atm layer processor. however, when txuclav toggles fr om ?high? to ?low?, it indicates that the very next cell (following the one that is currently being written into the transmit utopia interface block) cannot be accepted by the tx fifo. converse ly, once the txuclav output pin has retu rned to the logic ?1? level, it indicates that at least one more full cell may be wri tten into the txfifo by the atm layer processor. the atm layer processor is expected to poll the state of t he txuclav output pin towards the end of transmission of the cell currently being written and to proceed with writing the next atm cell into the transmit utopia interface block only if txuclav is at a logic ?high?. figure 11 presents a timing diagram th at illustrates the behavio r of various transmit utopia interface block signals, when the transmit utopia interface bloc k is operating in the ?ce ll-level? handshaking mode.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 157 figure 11 timing diagram of various transmit utopia interface block signals, when the transmit utopia interface block is operating in the ?cell level handshaking? mode txuclk txuclav txuenb * txudata [15:0] txusoc w26 w0 w1 w2 w23 w24 w25 w26 w22 x x 1 2 3 4 24 25 26 27 28 29 30 notes regarding figure 11: 1. the transmit utopia data bus is configured to be 16 bits wide. hence, the data, which the atm layer processor places on the transmit utopia data bus, is ex pressed in terms of 16-bit words: w0 - w26. 2. the transmit utopia interface block is configured to handle 54 bytes/cell. hence, figure 11 illustrates the atm layer processor writing 27 word s (w0 through w26) for each atm cell. in figure 11, the atm layer processor starts to write in a new atm cell, into the transmit utopia interface block, during clock edge #2. however, shortly after the atm layer processor has written in word w22 (at clock edge # 24), the txuclav output pin toggles ?low?. in the ?cell-level? handshaking mode, this means that atm layer processor is not permitted to write in the subsequent atm cell (e.g., the atm cell which is to follow the one that is currently being written into the transmit utopia interface block) into the transmit utopia interface block. hence, t he atm layer processor must complete writing in the current cell, and then halt with any further write operations to the transmit utopia interface block. therefore, the atm layer processor will proceed to write in words w23 thr ough w26 and then negate the txuenb* signal after clock edge #28. at this point, the atm layer processor must wait until the txuclav output pin toggles ?high? once again; before writing in the next atm cell. using the ?transmit utopia de-skewing? pll 2.2.1.3.4 utopia modes of operation (single phy and multi-phy operation) the xrt94l33 can be configured to support either si ngle-phy or multi-phy operation. each of these operating modes is discussed below. 2.2.1.3.5 single phy operation the xrt94l33 permits the user to configure it to operat e in either the ?single-phy? or ?multi-phy? mode. the user can configure the chip to operate in the ?singl e-phy? mode by setting bit 6 (multi-phy mode) to ?0?; as illustrated below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 158 transmit utopia control register ? byte 0, address = 0x0583 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level multi-phy mode back-to- back polling enable direct status access transmit utopia data bus width[1:0] cell_size_sel[1:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 0 0 0 1 1 x x note: this configuration setting does not apply to the receive utopia interface block. t herefore the user will also need to configure the receive utopia interface block in to the single-phy mode, as described in section _. in single-phy mode operation, the atm layer processo r is pumping data into and receiving data from only one phy-layer device, as depicted below in figure 22. figure 12 simple illustration of single - phy mode operation xrt95l34 atm switch (atm layer device) txudata[15:0] rxudata[15:0] txuclav txldata_p txldata_n rxldata_p rxldata_p txflow control input to/from optical transceiver rxuclav txusoc txuenb* txuprty txuclk rxuclk rxusoc rxuenb* rxuprty rxflow control input rx start of cell input tx start of cell output rx read output enable signal tx write enable output rx utopia data bus parity tx utopia data bus parity rx fifo clock signal tx fifo clock signal rx atm cell data tx atm cell data this section presents a detailed description of the tran smit utopia interface bloc k operating in the ?single- phy? mode. a description of the receive utopia in terface block operating in the ?single-phy? mode is presented in section _. whenever the transmit utopia interface block has been configured to operate in the single-phy mode, and whenever the atm layer processo r wishes to write one or a series of atm cells to the transmit utopia interface block, it must do the following. 1. check the level of the txuclav output pin upon each rising edge of txuclk. if the txuclav output pin is at a logic ?high? then there is available space in the tx fifo for more atm cell data and the atm layer processor may begin writing cell data to the transmit utopia interface block. however, if the txuclav pin is ?low?, then the tx fifo is too full to accept anymore data and the atm layer processor must wait until txuclav toggles ?high? before writing any cell data to the transmit utopia interface block. 2. apply the first byte (or word) of the new cell to the transmit utopia data bus. the atm layer processor must designate this byte (or word) as the beginning of a new cell, by pulsing the txusoc input pin ?high? for one period of txuclk.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 159 note: the transmit utopia interface block will sample and la tch the state of the txusoc input pin upon the rising edge of txuclk. therefore, if the txuclk to txusoc ou tput delay (of the atm layer processor) is 1ns or more, then the atm layer processor should update the state of the ?txusoc? input pin (of the xrt94l33) upon the rising edge of txuclk. 3. apply the odd-parity value of this first byte (or word), currently residing on the transmit utopia data bus, to the txuprty input pin. this should be done concurrently with pulsing the txusoc input pin ?high?. note: the transmit utopia interface block will sample and latc h the state of the ?txuprty ? input pin upon the rising edge of txuclk. therefore, if the txuclk to txuprty output delay (of the atm layer processor) is 1ns or more, then the atm layer processor should update the state of the ?txuprty? input pin (of the xrt94l33) upon the rising edge of ?txuclk?. 4. assert the ?transmit utopia data bus? - write enable signal, txuenb*. this step should also be done concurrently wi th pulsing the txusoc input pin ?high?. when writing the subsequent bytes (w ord) of the cell, the atm layer pr ocessor must repeatedly exercise steps 3 and 4, of the above list. since the xrt94l33 is always operating in the cell -level handshake mode, t hen the atm layer processor should check the level of the txuclav signal, as it nears completion of writing in a given cell. if ?txuclav? is ?high? then the atm layer processor can finish writing the current cell into the ?transmit utopia interface? block. afterwards, the atm layer pr ocessor may proceed to write in the contents of the very next ?outbound? atm cell into the transmit utopia interface block. conversely, if ?txuclav? is ?low? then the atm layer proc essor should finish writing the current atm cell data into the ?transmit utopia interface? block. a fterwards, the atm layer processor must negate the ?txuenb*? input pin and halt writing any more atm cell da ta into the ?transmit utopia interface? block, until the txuclav output pin toggles ?high? again. the above-mentioned procedure is also depicted in flow -chart form in figure 13 and in timing diagram form in figure 14.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 160 figure 13 flow chart depicting the approach that the atm layer processor should take when writing atm cell data into the transmit utopia interface block, when the xrt94l33 is operating in the single phy mode start check the level of the txuclav pin. is txuclav sampled ?high?? is this the first byte (word) of a new cell? is the current cell complete? is there anymore cells to write ? end assert the txusoc input pin place the first byte (word) on the transmit utopia data bus. place the odd-parity value of this byte (word) on the txuprty input pin assert the ?transmit utopia data bus write enable? pin, txuenb*. perform all of the following, concurrently writing the first byte/word of a cell perform all of the following, concurrently place the first byte (word) on the transmit utopia data bus. place the odd-parity value of this byte (word) on the txuprty input pin assert the ?transmit utopia data bus write enable? pin, txuenb*. writing the remaining bytes/ words of a cell no yes yes no no no yes yes
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 161 figure 14 timing diagram of atm layer processor writing atm cell data into the transmit utopia data bus, (single - phy mode) txuclk txuclav txuenb * txudata [15:0] txusoc w26 w0 w1 w2 w23 w24 w25 w26 w22 x x 1 2 3 4 24 25 26 27 28 29 30 notes regarding figure 14 : 1. the transmit utopia data bus is configured to be 16 bits wide. hence, the data, which the atm layer processor places on the transmit utopia data bus, is expressed in terms of 16-bit words: w0 - w26. 2. the transmit utopia interface bl ock is configured to handl e 54 bytes/cell. hence, figure 24 illustrates the atm layer processor writing 27 word s (w0 through w26) for each atm cell. final comments on single-phy operation the important thing to note about the single-phy mode is t hat the txuclav pin is used as a data flow control pin, and has a role somewhat similar to rts (request to send) in rs-232 based data transmission. the txuclav pin will have a slightly different role when the xrt94l33 is operating in the multi-phy mode. the atm layer processor is expected to poll the txuclav output pin during the last four ?txuclk? periods (while writing a given atm cell into the transmit utopia interface block) prior to writing the next atm cell to the txfifo. 2.2.1.3.6 multi phy operation the xrt94l33 permits the user to configure it to operate in the ?multi-phy? mode. this can be accomplished by setting bit 6 (multi-phy mode), within the ?transmit utopia control register ? byte 0? to ?1? as depicted below. transmit utopia control register ? byte 0, address = 0x0483 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level multi-phy mode back-to- back polling enable direct status access transmit utopia data bus width[1:0] cell_size_sel[1:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 0 0 1 1 x x note: this configuration setting does not apply to the receive utopia interface block. ther efore, the user will also need to configure the receive utopia interface block in to the ?multi-phy? mode, as described in section _. in the ?multi-phy? operating mode, the atm layer proces sor may be writing data into and reading data from several uni (e.g., phy-layer) devices in parallel. figure 12 presents an illustration of a simple ?multi-phy system? consisting of a single atm layer processor be ing interfaced to two (2) uni devices. when the
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 162 xrt94l33 is operating in the multi-phy mode, the transmi t utopia interface block will support two kinds of operations with the atm layer processor: ? polling for ?available? uni (phy layer) devices. ? selecting which uni (out of several possib le uni devices) to write atm cell data to. each of these operations is discussed in the sections below. however, prior to discussing each of these operations, the reader must understand the following. ?multi-phy? operation involves the use of one (1) atm layer processor and several uni (or phy-layer) devices, within a system. the atm layer processor is expected to read/write atm cell data from/to these uni devices. hence, ?multi-phy? operation requires , at a minimum, some means for the atm layer processor to uniquely identify a particular uni device (among all of the uni devices within the ?multi-phy? system) that it wishes to ?poll?, write atm cell data to, or read atm cell data from. actually, ?multi-phy? operation provides an addressing scheme allows th e atm layer processor to uniquely identify ?utopia interface blocks? (e.g., transmit and receive) within all of the uni devices, oper ating in the ?multi-phy? system. in order to uniquely identify a given ?utopia interface block?, within a ?multi-phy? system, each ?transmit and receive utopia interface blocks are a ssigned a 5-bit ?utopia address? value. the user assigns this address value to a particular ?transmit utopia interface block? by writing this address value into the ?transmit utopia address register? (address = 0x0593) and appropriate data into the ?transmit utopia port address? regi ster (address = 0x0597); within its ?host? xrt94l33; per the procedure (as presented below). the bit-format of the ?transmit ut opia address register? and ?transmit port address? register is presented below. transmit utopia address register (address = 0x0593) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused tx_utopia_addr[4:0] ro ro ro r/w r/w r/w r/w r/w 0 0 0 x x x x x transmit utopia port number register (address = 0x0597) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused tx_utopia_port_number[4:0] r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 x x x x x 2.2.1.3.7 assigning transmit utopia addresses to each sts-3c channel within the xrt94l33 the xrt94l33 can be configured to function as a three channel atm uni over either an sts-3 signal or an sts-3c. as a consequence, for multi-phy operati on, the xrt94l33 can be assigned as many as four ?transmit utopia addresses? at a gi ven time (one for each sts-1 channel). the user can assign a ?transmit utopia address? va lue to a given channel, within the xrt94l33 by executing the following steps. step 1 ? assign a ?transmit utopia address? to channel 0 the user can accomplish this by doing the following. step 1a ? set bits 0 through 4 (?tx_utopia_port_number[4:0]?) within the ?transmit utopia port number register? to ?0x00?; as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 163 transmit utopia port number register (address = 0x0597) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused tx_utopia_port_number[4:0] r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 this step configures an internal ?transmit utopia a ddress assignment? pointer to point to ?sts-3c channel 0? within the xrt94l33. step 1b ? set bits 0 through 4 (?tx_utopia_addr[4 :0]?) within the ?transmit utopia address? register to the desired ?multi-phy? address value for this channel [a4, a3, a2, a1, a0]; as depicted below. transmit utopia address register (address = 0x0593) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused tx_utopia_addr[4:0] ro ro ro r/w r/w r/w r/w r/w 0 0 0 a4 a3 a2 a1 a0 this step configures the transmit utopia address, of the value [a4, a3, a2, a1, a0] to be assigned to channel 0. notes: during this step, the user can write in any value, between 0x00 and 0x1e, prov ided this ?multi-phy address? is unique among all of the transmit utopia interfac e addresses within a ?multi-phy? system. use of the value ?0x1f? is not permitted. these steps do not assign a receive utopia address value to the sts-3c channel 0. this assignment must be performed separately per the ?receive utopia address? assignment instructions, presented in section _. once the user has executed steps 1a and 1b, then sts-3c channel 0 within the xrt94l33 has been assigned the ?transmit utopia addr ess? of [a4, a3, a2, a1, a0]. step 2 ? assign a ?transmit utopia address? to sts-3c channel 1 the user can accomplish this by doing the following. step 2a ? set bits 0 through 4 (?tx_utopia_port_number[4:0]?) within the ?transmit utopia port number register? to ?0x01?; as depicted below. transmit utopia port number register (address = 0x0597) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused tx_utopia_port_number[4:0] r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 1 this step configures an internal ?transmit utopia a ddress assignment? pointer to point to ?sts-3c channel 1? within the xrt94l33.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 164 step 2b ? set bits 0 through 4 (?tx_utopia_addr[4 :0]?) within the ?transmit utopia address? register to the desired ?multi-phy? address value for this channel [b4, b3, b2, b1, b0]; as depicted below. transmit utopia address register (address = 0x0593) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused tx_utopia_addr[4:0] ro ro ro r/w r/w r/w r/w r/w 0 0 0 b4 b3 b2 b1 b0 this step configures the transmit utopia address, of the value [b4, b3, b2, b1, b0] to be assigned to channel 1. notes: 1. during this step, the user can wr ite in any value, between 0x00 and 0x1e, provided this ?multi-phy address? is unique among all of the transmit utopia a ddresses within a ?multi-phy? system. 2. use of the value ?0x1f? is not permitted. 3. these steps do not assign a receive utopia address va lue to sts-3c channel 1. this assignment must be performed separately per the ?receive utopia addre ss assignment? instructions presented in section _. once the user has executed steps 2a and 2b, then sts-3c channel 1 within the xrt94l33 has been assigned the ?transmit utopia addr ess? of [b4, b3, b2, b1, b0]. step 3 ? assign a ?transmit utopia address? to sts-3c channel 2 the user can accomplish this by doing the following. step 3a ? set bits 0 through 4 (?tx_utopia_port_number[4:0]?) within the ?transmit utopia port number register? to ?0x02?; as depicted below. transmit utopia port number register (address = 0x0597) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused tx_utopia_port_number[4:0] r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0 0 0 1 0 this step configures an internal ?transmit utopia a ddress assignment? pointer to point to ?sts-3c channel 2? within the xrt94l33. step 3b ? set bits 0 through 4 (?tx_utopia_addr[4 :0]?) within the ?transmit utopia address? register to the desired ?multi-phy? address value for this channel [c4, c3, c2, c1, c0]; as depicted below. transmit utopia address register (address = 0x0593) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused tx_utopia_addr[4:0] ro ro ro r/w r/w r/w r/w r/w 0 0 0 c4 c3 c2 c1 c0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 165 this step configures the transmit utopia address, of the value [c4, c3, c2, c1, c0] to be assigned to sts- 3c channel 2. notes: 1. during this step, the user can wr ite in any value, between 0x00 and 0x1e, provided this ?multi-phy address? is unique among all of the transmit utopia interf ace addresses within a ?multi-phy? system. 2. use of the value ?0x1f? is not permitted. 3. these steps do not assign a receive utopia address va lue to sts-3c channel 2. this assignment must be performed separately per the ?receive utopia addre ss assignment? instructions presented in section _. once the user has executed steps 3a and 3b then sts-3c channel 2 within the xrt94l33 has been assigned the ?transmit utopia addr ess? of [c4, c3, c2, c1, c0]. step 4 ? assign a ?transmit utopia address? to sts-3c channel 3 the user can accomplish this by doing the following. step 4a ? set bits 0 through 4 (?tx_utopia_port_number[4:0]?) within the ?transmit utopia port number register? to ?0x03?; as depicted below. transmit utopia port number register (address = 0x0597) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused tx_utopia_port_number[4:0] r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0 0 0 1 1 this step configures an internal ?transmit utopia a ddress assignment? pointer to point to ?sts-3c channel 3? within the xrt94l33. step 4b ? set bits 0 through 4 (?tx_utopia_addr[4 :0]?) within the ?transmit utopia address? register to the ?multi-phy? address value for this channel [d4, d3, d2, d1, d0]; as depicted below. transmit utopia address register (address = 0x0593) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused tx_utopia_addr[4:0] ro ro ro r/w r/w r/w r/w r/w 0 0 0 d4 d3 d2 d1 d0 this step configures the transmit utopia address, of the value [d4, d3, d2, d1, d0] to be assigned to sts- 3c channel 3. notes: 1. during this step, the user can write in any value, bet ween 0x00 and 0x1e provided this ?multi-phy address? is unique among all of the transmit utopia interf ace addresses within a ?multi-phy? system. 2. use of the value ?0x1f? is not permitted. 3. these steps do not assign a receive utopia address va lue to sts-3c channel 3. this assignment must be performed separately per the ?receive utopia addre ss assignment? instructions presented in section _. once the user has executed steps 4a and 4b then sts-3c channel 3 within the xrt94l33 has been assigned the ?transmit utopia addr ess? of [d4, d3, d2, d1, d0].
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 166 2.2.1.3.8 atm layer processor ?polling? of the unis, in the multi-phy mode in this section, the various multi-ph y operations (e.g., polling and selection for writing) will be first discussed for a ?conceptual multi-phy? system, and then later, sp ecifically for the xrt94l33. when the xrt94l33 is operating in the ?multi-phy? mode, then the transmit utopia interface bl ock will automatically be configured to support ?polling?. ?polling? allows an atm layer pr ocessor (which is interfaced to several uni devices) to determine which unis are capable of receiving and handlin g additional atm cell data, at any given time. the manner in which the atm layer processor ?polls? its un i devices, (per the ?conceptual multi-phy? system) follows. figure 15 an illustration of the ?c onceptual multi-phy system cons isting of uni devices #1 and #2 txudata[15:0] txuaddr[4:0] txuprty txuenb* txusoc txuclav rxudata[15:0] rxuaddr[4:0] rxuprty rxuenb* rxusoc rxuclav uni # 1 txaddr = 0x00 rxaddr = 0x01 txudata[15:0] txuaddr[4:0] txuprty txuenb* txusoc txuclav rxudata[15:0] rxuaddr[4:0] rxuprty rxuenb* rxusoc rxuclav txaddr = 0x02 rxaddr = 0x03 txdata[15:0] ut_addr[4:0] tx_parity tx_ut_wr* tx_soc_out txclav_in rxdata[15:0] rx_parity rx_ut_rd* rx_soc_in rxclav_in atm layer processor uni # 2 2.2.1.3.9 atm layer processor ?polling? in a conceptual multi-phy system figure 26 depicts a ?multi-phy? system consisting of a single atm layer processor and two (2) uni devices, which are designated as ?uni #1? and ?u ni #2?. in this figure, both of the unis are connected to the atm layer processor via a common ?transmit utopia? da ta bus, a common ?receive utopia? data bus, a common ?txuclav? line, a common ?rxuclav? line, as well as common txuenb*, rxuenb*, txusoc and rxusoc lines. the atm layer processor will also be addressing both the transmit and receive utopia interface blocks via a common ?utopia? address bus (u t_addr[4:0]) therefore, the transmit and receive utopia interface blocks, within a given uni might ha ve different addresses; as depicted in figure 26. the utopia address values, that have been assigned to each of the transmit and receive utopia interface blocks, within figure 15, are listed below in table 13.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 167 table 13 utopia address values of the utopia interface blocks illustrated in figure 26. b lock utopia a ddress v alue transmit utopia interface block - uni #1 0x00 receive utopia interface block - uni #1 0x01 transmit utopia interface block - uni #2 0x02 receive utopia interface block - uni #2 0x03 recall, that the transmit utopia in terface blocks were assigned these addresses by writing these values into registers that are similar to the ?transmit utop ia port number (address = 0x0597) and the transmit utopia address register? (address = 0x0593) within these uni devic es. the discussion of the receive utopia interface blocks, within unis #1 and #2 is presented in section _. polling operation consider that the atm layer processor is currently writing a co ntinuous stream of atm cell data into uni #1. while writing this cell data into uni #1, the atm layer pr ocessor can also ?poll? uni #2 for ?availability? (e.g., tries to determine if the atm layer processor can write any more atm ce ll data into the ?transmit utopia interface block? within uni #2). the atm layer processor?s role in the ?polling? operation the atm layer processor accomplishes this ?po lling? operation by executing the following steps. 1. assert the txuenb* input pin (if it is not asserted already). the uni device (being ?polled?) will know that this is only a ?polling? operation, if the txuenb* input pin is asserted, prior to detecting its utopia address on the ?utopia address? bus (txuaddr[4:0]). 2. the atm layer processor places the address of the transmit utopia interface block of uni #2 onto the utopia address bus, ut_addr[4:0], 3. the atm layer processor will then check the value of its ?txuclav_in? input pin (see figure 24). the atm layer processor is suppose to check the stat e of the ?txuclav? signal, one ?txuclk? period after placing the utopia address (corresponding to a particular uni device) on the ?txuaddr[4:0]? input pins. if ?txuclav? is sampled ?high? then this means that this particular uni device cont ains sufficient empty space within its txfifo to accept another atm cell from t he atm layer processor. conversely, if txuclav is sampled ?low? then this means that this particular uni device does not contain enough empty space within its txfifo to accept another atm cell from the atm layer processor. the uni devices role in the ?polling? operation uni #2 will sample the signal levels placed on its tx utopia address input pins (txuaddr[4:0]) on the rising edge of its ?transmit utopia interface block? clock i nput signal, txuclk. afterwards, uni #2 will compare the value of these ?transmit utopia address bus input pin? signals with that of the contents of its ?tx utopia address register (address = 0x0593). if these values do not match, (e.g., txuaddr[4:0] 0x02) then uni #2 will keep its ?txuclav? output signal ?tri-stated?; and will continue to sample its ?transmit utopia address bus input? pins; with each rising edge of txuclk. if these two values do match, (e.g., txuaddr[4:0] = 0x02) then uni #2 will drive its ?txuclav? output pin to the appropriate level, reflecting its txfi fo ?fill-status?. since the uni is only operating in the ?cell level handshaking? mode, the uni w ill drive the txuclav output signal ?high? if it is capable of receiving at least one more complete cell of data from the atm layer proces sor. conversely, the uni will drive the ?txuclav?
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 168 output signal ?low? if its txfifo is too full and is incapable of receiving one more complete cell of data from the atm layer processor. when uni #2 has been selected for ?polling?, uni #1 w ill continue to keeps its ?t xuclav? output signal ?tri- stated?. therefore, when uni #2 is dr iving its ?txuclav? output pin to the ap propriate level; it will be driving the entire ?txuclav? line, within the ?multi-phy? system. consequently, uni#2 will also be driving the ?txuclav_in? input pin of the atm layer processor (see figure 26). if uni #2 drives the ?txuclav? line ?low?, upon the appl ication of its address on the utopia address bus, then the atm layer processor will ?learn? that it cannot write any more cell data to this uni device; and will deem this device ?unavailable?. however, if uni #2 driv es the txuclav line ?high? (during ?polling?), then the atm layer processor will know that it can write more atm cell data into th e transmit utopia interface block, of uni # 2. figure 16 presents a timing diagram, that depicts the behavior of the atm layer processor?s and the uni?s signals during polling. figure 16:timing diagram illustrating the behavior of various signals from the atm layer processor and the uni, during polling txuclk txuaddr[4:0] txuclav txuenb* txudata[15:0] txusoc 0x00 1fh 0x02 0x1f 0x00 0x02 0x1f 0x02 0x00 0x1f 0x00 0x02 w27 w0 w1 w2 w3 w4 w5 w6 w7 w8 w9 w10 0x00 0x02 0x00 0x02 0x02 0x00 0x00 1 2 3 4 5 6 7 8 9 10 11 12 notes regarding figure 16: 1. the transmit utopia data bus is configured to be 16 bits wide. hence, the data, which the atm layer processor places on the transmit utopia data bus, is expr essed in terms of 16-bit words: (e.g., w0 - w26.) 2. the transmit utopia interface bl ock is configured to handl e 54 bytes/cell. hence, figure 27 illustrates the atm layer processor writing 27 word s (w0 through w26) for each atm cell. 3. the atm layer processor is currently writing atm cell data to the transmit utopia interface block, within uni #1 (txuaddr[4:0] = 0x00) during this ?polling process?. 4. the txfifo, within uni#2?s transmit utopia in terface block (txuaddr[4:0] = 0x02) is incapable of receiving any additional atm cell data from the atm layer processor. hence, the txuclav line will be driven ?low? whenever this particular transmit utopia interface block is ?polled?. 5. the transmit utopia address of 0x1f (e.g., the null address), is not associ ated with any uni device, within this ?multi-phy? system. henc e, the txuclav line is tri-stated whe never this address is ?polled?. note: although figure 26 depicts connections between the rece ive utopia interface block pins and the atm layer processor; the receive utopia interf ace block operation, in the multi-phy mode, will not be discussed in this section. please see section _ for a discussion on the receive utopia interfac e block during multi-phy operation. 2.2.1.3.10 atm layer processor ?polling? with the xrt94l33 in figure 15, a simple illustration of the ?conceptual multi-phy? system consisting of two single-channel uni devices was presented. in reality, a given multi-phy system can or will consist of numerous ?multi-channel? uni devices. the xrt94l33 is an example of this, being a ?4-channel? uni device. therefore, the
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 169 xrt94l33 can be thought of as consisting of four atm unis within a single package (one for each sts-3c port within the device). it is important to note that although the xrt94l33 consists of a single ?transmit utopia interface? block, the xrt94l33 can be assigned four unique (4) transmit utopia addresses as presented in section 4.2.1.2.1.4.2.1. 2.2.1.3.11 writing atm cell data into a different uni after the atm layer processor has ?polled? each of the uni devices, within its system, it must now select a uni, and begin writing atm cell data to that device. the atm layer processor makes its selection and begins the writing process by: 1. applying the utopia address of the ?targe t? uni on the ?transmit utopia address bus? (txuaddr[4:0]). negate the txuenb* signal. this step causes the ?addr essed? uni to recognize that it has been selected to receive the next set of atm cell data from the atm layer processor. assert the txuenb* signal. assert the txusoc input pin. begin applying the atm cell data in a byte-wide (or wo rd-wide) manner to the transmit utopia data bus (txudata[15:0]). at this point, atm cell data is now being written into the txfifo associated with the newly selected uni. figure 17 presents a flow-chart t hat depicts the ?uni device selectio n and write? process in multi-phy operation. figure 17: flow-chart of the ?uni device selection and write procedure? for the multi-phy operation start poll all unis within the ?multi-phy? system. determine which unis are ?available? select ?available? uni 1. apply utopia address of the transmit utopia interface block onto the ?utopia address? bus. 2. negate the txuenb* signal begin writing atm cell data into ?selected? uni 1. assert txuenb* 2. place first byte/word of atm cell onto the ?transmit utopia data bus & assert txusoc continue to write atm cell data check the txuclav level after writing 48 bytes of cell data. is txuclav ?high? ? continue to poll uni and wait for txuclav to toggle ?high? is txuclav ?high? ? is there any more atm cell data to be written to selected uni? yes no yes yes no no figure 18 presents a timing diagram th at illustrates the beh avior of various ?transmit utopia interface block? signals; during the ?multi-phy? uni device selection and write operation.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 170 figure 18: timing diagram of the transmit utopia data and address bus signals, during the ?multi- phy? uni device selection and write operations txuclk txuaddr[4:0] txuclav txuenb* txudata[15:0] txusoc 0x00 0x1f 0x02 0x1f 0x00 0x02 0x1f 0x00 0x02 0x1f 0x02 0x00 w0 w1 w2 w3 w4 w5 w6 w26 w25 w24 w23 cell transmitted to 0x02 cell transmitted to 0x00 0x00 0x02 0x00 0x02 0x00 0x02 0x02 1 2 3 4 5 6 7 8 9 10 11 12 notes regarding figure 18: 1. the transmit utopia data bus is configured to be 16 bits wide. hence, the data, which the atm layer processor places on the transmit utopia data bus, is expressed in terms of 16-bit words (e.g., w0 - w26). 2. the transmit utopia interface bl ock is configured to handl e 54 bytes/cell. hence, figure 29 illustrates the atm layer processor writ ing 27 words (e.g., w0 through w26) for each atm cell. in figure 29, the atm layer processo r is initially writing atm cell data to the transmit utopia interface block within uni #2 (txuaddr[4:0] = 0x02). however, the atm layer processor is also polling the transmit utopia interface block within uni #1 (txaddr[4:0] = 0x00) and the ?null? address of 0x1f. the atm layer processor completes its writing of the cell to uni #1 at clock edge #4. afterwards, the atm layer processor will cease to write any more cell data to uni #1, and will begin to write th is data into uni #2 (txuaddr[4:0] = 0x02). the atm layer processor will in dicate its intentions to select a new uni device for wr iting by negating the txuenb* signal, at clock edge #5 (s ee the shaded portion of figure 29). at this time, uni #1 will notice two things: 1. the utopia address for the transmit utopia inte rface block, within uni #1 is on the transmit utopia address bus (txuaddr[4:0] = 0x00). 2. the txuenb* signal has been negated. uni #1 will interpret this signaling as an indication t hat the atm layer processor is going to be performing write operations to it. afterwards, the atm layer pr ocessor will begin to write atm cell data into transmit utopia interface block, within uni #1. 2.2.1.4 utopia l evel 3 o peration of the t ransmit utopia i nterface b lock b ack - to -b ack p olling if the transmit utopia interface bloc k has been configured to operate in the utopia level 3 mode, then it can be configured to support ?back-to-back? polling. utopia level 2 specifications mandate that the atm lay er processor interleave the application of utopia addresses with the ?nul l? address of 0x1f. if ?back-to-back? polling is selected, then the at m layer processor does not need to interleave the application of utopia addresses with the ?null? addre ss. instead, the atm layer processor can poll each of the unis, by applying a different ?utopia address? valu e, with each cycle of ?txuclk? (e.g., in a ?back-to- back? manner). the user can configure the ?transmit utopia interface? block to support ?back-to-back? polling by setting bit 5 (back-to-back polling enable) within the ?transmit utopia control? register, to ?1? as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 171 transmit utopia control register ? byte 0, address = 0x0483 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level multi-phy mode back-to- back polling enable direct status access transmit utopia data bus width[1:0] cell_size_sel[1:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 0 1 1 x x 2.2.2 transmit atm cell processor block the next functional block, within the transmit path of the xrt94l33 is the transmit atm cell processor block. figure 19 presents an illustration of the xrt94l33 functional block diagram, with the ?transmit atm cell processor block? highlighted. figure 19: illustration of the xrt94l33 functional block diagram, with the transmit atm cell processor block highlighted transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3 toh processor block receive sts-3 toh processor block transmit sts-3 toh processor block transmit sts-3 toh processor block receive sts-3c poh processor block receive sts-3c poh processor block transmit sts-3c poh processor block transmit sts-3c poh processor block sts-3 telecom bus interface block sts-3 telecom bus interface block sts-3 pecl interface block sts-3 pecl interface block sts-3 cdr block sts-3 cdr block xrt94l33 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 172 figure 20 presents a simple block diag ram of the transmit atm cell proces sor block (with the external pins indicated). figure 20: simple illustration of the transmit atm cell processor block and th e associated external pins transmit atm cell processor block txcelltxed txgfcclk txgfcmsb txgfc from transmit utopia interface block to transmit sts-3c/sts-12c poh processor block a very brief description of the transmit atm cell processor block the transmit atm cell processor block reads in atm cells from the transmit utopia fifo (txfifo) within the transmit utopia interface block. immediately afte r reading in a given cell from the txfifo, the transmit atm cell processor will compute and verify the parity value of each byte or (16-bit) word of this atm cell. if the transmit atm cell processor block detects a parity error within one of these bytes then (or 16-bit words) then the entire cell will be (optionally) discarded. a fterwards, each atm cell (which is not discarded due to parity error) will be processed through a ?user-conf igurable? filter. if the cell does not meet t he ?user-cell? filtering criteria, then it will be discarded. next, the atm cell will be processed through both the ?transmit data path? and the ?transmit cell extraction? processor, in parallel. the manner in which this atm cell is handled (via each of these paths) is briefly described below. 2.2.3 t he t ransmit c ell e xtraction p rocessor the user cell filter blocks (within the transmit atm ce ll processor block) permit the user to configure it to copy (e.g., replicate) certain atm cells; and route these ?copies? of atm cells to the ?transmit cell extraction buffer?. the ?transmit cell extraction processor permit s the user to read out the contents of these ?copied? atm cells via the microprocessor interface.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 173 2.2.4 t he t ransmit d ata p ath all atm cells that successfully pass through ?parity ch ecking? and ?user cell filtering? will be processed via the ?hec byte calculation & insertion? block. in this case, the transmit atm cell processor block will optionally compute and insert the hec byte into the fifth octet position within each outbound atm cell and, optionally scrambles the cell payload bytes. when the txfifo does not contain a full cell, the transmit atm cell processor block will then proceed to read out the contents of the ?transmit cell insertion? buffer. once the ?transmit cell insertion? buffer has been depleted, then the ?idle cell generator? block will begin to generate and transmit ?idle cells? via the transmit data path. finally, the transmit atm cell proc essor is also equipped with a serial input port that permits the user to externally insert the value of the gfc (generic flow control) field for each outbound cell. figure 30 presents an illustration of the functional block diagram of the transmit atm cell processor block and the associated external pins. a detailed description of the transmit at m cell processor block is presented below. 2.2.4.1 f unctional d escription of the t ransmit atm c ell p rocessor this section presents an in-depth functional descrip tion of the transmit atm cell processor block. additionally, this section presents all of the configur ation options associated with the transmit atm cell processor block. the transmit atm cell processor consists of the following functional blocks. ? parity checker block ? transmit user cell filter block ? hec byte calculation & insertion block ? the transmit cell insertion buffer/processor ? the transmit cell extraction buffer/processor ? cell payload scrambler block ? idle cell generator block ? ?transmit gfc nibble-field? serial input port figure 21 presents an illustration of the functional bloc k diagram of the transmit atm cell processor block; with each of these ?above-mentioned? functional blocks noted. each of these ?sub-blocks? will be disc ussed in some detail below . however, before we get too much into the detailed functional description of the transmit atm cell processor block; the user must note that the transmit atm cell processor block will not even functi on unless the user enables the ?transmit atm cell processor? block for operation. t he user can enable the transmit atm cell processor block by setting bit 0 (transmit atm cell processor enable), within the ?t ransmit atm cell processor block ? transmit atm control register ? byte 2? to ?1? as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 174 transmit atm cell processor block ? transmit atm control register ? byte 2 (address = 0xnf01) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused transmit atm cell processor enable r/o r/o r/o r /o r/o r/o r/o r/w 0 0 0 0 0 0 0 1 figure 21: functional block diagram of the transmit atm cell processor block parity checker block parity checker block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte calculation & insertion block hec byte calculation & insertion block cell payload scrambler block cell payload scrambler block txfifo txfifo transmit utopia interface block microprocessor interface block microprocessor interface block idle cell generator idle cell generator main data path to transmit sonet/sts-3c poh processor block transmit gfc nibble-field input port block transmit gfc nibble-field input port block txgfc input port 2.2.5 t he p arity c hecker b lock whenever the atm layer proc essor writes atm cell data into the transm it utopia interface block; it will do so by placing a sequence of bytes or (16-bit) words unto the transmit ut opia interface data bus (txudata[15:0]). as the atm layer processor is placing each byte or word (or a given atm cell); into the transmit utopia data bus, it is expected to comput e the odd parity of each of these bytes or words. additionally, the atm layer processor is expected to ap ply this parity value to the ?txuprty? input pin, coincident with placing the corresponding byte or wo rd (of atm cell data) onto the transmit utopia data bus. the transmit utopia interface block will latch the cont ents of a given byte or word (of atm cell data) upon the rising edge of ?txuclk?. as the transmit utopia interface block samples and latches each byte or word
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 175 of atm cell data, it is also sampling and latching the va lue of the corresponding parity bit (via the ?txuprty? input pin). all sampled byte/words and their co rresponding sampled parity value will be loaded into the ?txfifo? for further processing by the transmit atm cell processor block. as the transmit atm cell processor block reads out t he contents of the atm cells (and corresponding parity information) from the txfifo, it will route this data to the ?par ity-checker? block. the parity check block will then compute the parity value of each by te or 16-bit word (of atm cell data that is read from the txfifo). afterwards, the parity checker block will then compare the value of this ?locally-computed? parity bit, with the corresponding sampled parity value (originating from the ?txuprty? input pin). if the ?locally-computed? and the ?atm layer processor? s upplied parity values match then this byte (or 16-bit word) of atm cell data is deemed to be ?error-free? and the parity-checker block will proceed to check and verify the parity value of the very next byte (or 16-bit wo rd) of atm cell data. on the other hand, if there is a discrepancy between the ?locally-compu ted? the ?atm layer processor? su pply parity values, then the ?parity- checker? block will declare a ?transmit utopia interface ? parity error? event, and this entire atm cell is subject to being discarded (depending upon user configuration). 2.2.5.1 h ow the t ransmit atm c ell p rocessor b lock verifies p arity the transmit atm cell processor block provides the user with the following parity-checking features. ? to disable parity-checking altogether. ? to verify odd parity ? to verify even parity ? to retain cells that contain parity errors ? to discard cells that contain parity errors each of these ?transmit atm cell processor? block parity options are discussed below. 2.2.5.2 e nabling /d isabling p arity c hecking within the t ransmit c ell p rocessor b lock the transmit atm cell processor block permits the user to either enable or disable the ?parity verification? of all bytes/words of atm cells that have been read out of t he txfifo. the user can accomplish this by writing the appropriate data into bit 5 (parity check enable) wi thin the transmit atm control ? byte 0 register; as depicted below. transmit atm control ? byte 0 register (address = 0xnf03) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 hec byte invert hec byte check enable parity check enable discard cell upon parity error odd parity unused cell payload scramble enable r/w r/w r/w r/w r/w r/o r/o r/w 0 0 x 0 0 0 0 0 setting this bit-field to ?1? configures the transmit at m cell processor block to check and verify parity of all incoming ?user? cells. conversely, setting this bit-fiel d to ?0? disables parity checking by the transmit atm cell processor block. 2.2.5.3 c onfiguring the t ransmit atm c ell p rocessor block to check o dd or e ven p arity the transmit atm cell processor block can be configured to check and verify either even or odd parity. the user can implement this selection by writing the appropriate value into bit 3 (odd parity) within the ?transmit atm control ? byte 0? register; as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 176 transmit atm control ? byte 0 register (address = 0xnf03) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 hec byte invert hec byte check enable parity check enable discard cell upon parity error odd parity unused cell payload scramble enable r/w r/w r/w r/w r/w r/o r/o r/w 0 0 1 0 x 0 0 0 setting this bit-field to ?1? configures the transmit ce ll processor block to check and verify ?odd? parity. conversely, setting this bit-field to ?0? configures the transmit cell processor block to check and verify ?even? parity. note: this bit-field is ignored if bit 5 (parity check enable) is set to ?0?. 2.2.5.4 c onfiguring the t ransmit atm c ell p rocessor block to d iscard c ells upon p arity e rrors the transmit atm cell processor block pe rmits the user to configure it to discard all cells that contain parity errors. the user can implement this selection by writ ing the appropriate value into bit 4 (discard cell upon parity error) within the ?transmit atm c ontrol ? byte 0? register; as depicted below. transmit atm control ? byte 0 register (address = 0xnf03) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 hec byte invert hec byte check enable parity check enable discard cell upon parity error odd parity unused cell payload scramble enable r/w r/w r/w r/w r/w r/o r/o r/w 0 0 1 x x 0 0 0 setting this bit-field to ?1? configures the transmit at m cell processor block to discard all cells that contain parity errors. conversely, setting this bit-field to ?0 ? configures the transmit atm cell processor block to retain all cells (even if t hey contain parity errors). note: this bit-field is ignored if bit 5 (parity check enable) is set to ?0?. 2.2.5.5 i nterrupts d ue to d etection of ?t ransmit utopia i nterface ? p arity e rrors the transmit atm cell processor block can be configured to generate an interrupt, anytime it detects a parity error, within a given cell. the user can accomplish th is by setting bit 0 (detection of parity error interrupt enable), within the transmit atm cell processor ? inte rrupt enable register to ?1?; as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 177 transmit atm cell processor ? interrupt enable register (address = 0xnf0f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt enable cell insertion interrupt enable cell extraction memory overflow interrupt enable cell insertion memory overflow interrupt enable detection of hec byte error interrupt enable detection of parity error interrupt enable r/o r/o r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 1 once the user has enabled the ?detection of parity e rror? interrupt, then the transmit atm cell processor block will generate an interrupt anytime it detects a parity error within a given byte (or 16-bit word) in a given incoming ?user cell?. whenever the transmit atm ce ll processor block generates this interrupt, it will indicate so by doing all of the following. 1. by toggling the ?int*? output pin ?low. 2. by setting bit 0 (detection of parity error interr upt status), within the ?transmit atm cell processor ? interrupt status register? to ?1?, as depicted below. transmit atm cell processor ? interrupt status register (address = 0xnf0b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt status cell insertion interrupt status cell extraction memory overflow interrupt status cell insertion memory overflow interrupt status detection of hec byte error interrupt status detection of parity error interrupt status r/o r/o rur rur rur rur rur rur 0 0 0 0 0 0 0 1 2.2.5.6 c ounting p arity e rrors for performance monitoring purposes, the user can keep track of the number of parity errors that have been detected over time, by periodically polling and reading out the contents of the ?transmit atm cell processor ? parity error count? register. this register is a 32-bit wi de, reset-upon-read regist er, that is incremented each time the transmit atm cell processor block detects a parity error in an incoming user cell. this register will increment up until it reaches the value of ?0x ffffffff?; at this point it w ill saturate at this value (e.g., cease to increment), until read again.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 178 transmit atm cell processor ? parity error count register ? byte 3 (address = 0xnf34) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 number of parity errors[31:24] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 transmit atm cell processor ? parity error count register ? byte 2 (address = 0xnf35) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 number of parity errors[23:16] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 transmit atm cell processor ? parity error count register ? byte 3 (address = 0xnf36) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 number of parity errors[15:8] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 transmit atm cell processor ? parity error count register ? byte 3 (address = 0xnf37) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 number of parity errors[7:0] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 2.2.6 t he t ransmit u ser c ell f ilter b lock once a given atm cell has successfully passed through the ?parity-checker? block, or has been read out of the ?transmit cell insertion? memory buffer, it will now be processed by the ?transmit user cell filter? block. figure 22 presents the functional block diagram of the transmit atm cell pr ocessor block with the ?transmit user cell filter? block highlighted.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 179 figure 22: illustration of the ?transmit atm ce ll processor? functional block diagram with the ?transmit user-cell filter? block highlighted parity checker block parity checker block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte calculation & insertion block hec byte calculation & insertion block cell payload scrambler block cell payload scrambler block txfifo txfifo transmit utopia interface block microprocessor interface block microprocessor interface block idle cell generator idle cell generator main data path to transmit sonet/sts-3c poh processor block transmit gfc nibble-field input port block transmit gfc nibble-field input port block txgfc input port the transmit atm cell processor block consists of four pa rallel user cell filters. these user cell filters are connected in parallel, in the sense that the entire ?transmit? atm cell tr affic will be presented to the inputs of each of the four ?user-cell? filters, at the same time . figure 23 attempts to clarify this phenomenon by presenting an illustration as to how each of these user cell filters is connected to the atm traffic.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 180 figure 23: an illustration of the configuration of the four transmit user cell filters within the transmit atm cell processor block to hec byte checker, transmit sonet/sts-3c poh processor block user cell filter # 0 user cell filter # 0 user cell filter # 3 user cell filter # 3 user cell filter # 2 user cell filter # 2 user cell filter # 1 user cell filter # 1 to cell extraction memory from parity checker and insertion memory blocks each of these four (4) user cell filters can be configur ed to analyze all of the header bytes, within a given atm cell. based upon the value of these header bytes (wit hin a given cell), each of the four user cell filter blocks can be configured to perform either of the following functions. ? to filter (e.g., discard) the cell ? to not filter (e.g., permit the cell to pass through, along the data path) the cell ? to replicate (or copy) the cell, and route the replicate cell to the ?transmit atm cell processor? block ? extraction processor block. ? to not replicate the cell. instructions on how to implement the following user cell filter options are presented below. ? enabling/disabling the user cell filter ? defining the user cell filter action ? defining the user cell filter sense ? specifying the user cell filter values
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 181 2.2.6.1 e nabling /d isabling the t ransmit u ser c ell f ilter the transmit atm cell processor block permits the user to either enable or disable each of the four transmit user cell filters. the user can accomplish this by wr iting the appropriate data into bit 3 (user cell filter enable), within the ?transmit atm filter control ? byte 0? register; as depicted below. transmit atm filter # 0, # 1, # 2, # 3 control ? byte 0 (address = 0xnf43, 0xnf53, 0xnf63, 0xnf73) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused user cell filter enable copy cell enable discard cell user cell filter sense r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x 0 0 0 note: as the bit-format table for the ?transmit atm filter cont rol ? byte 0? register implies, each of the four (4) transmit user cell filters can be individually enabled or disabled. further, each of these four transmit user cell filters can be individually configured to ei ther ?copy? or ?discard? cells (or both). setting this bit-field to ?1? enables the corresponding tr ansmit user cell filter. conversely, setting this bit- field to ?0? disables the ?transmit user cell filter?. if a given transmit user cell filter is enabled, then it will perform action on all incoming atm cells, based upon the settings of the remaining register bits within this register; and that within both the ?transmit atm filter control ? pattern? and ?transmit atm filter cont rol ? check? registers. conversely, if the given transmit user cell filter is disabled, then all user cells will pass throu gh the transmit user cell filter, and towards the ?hec byte calculation & insertion? blo ck without any such actions performed on these cells. 2.2.6.2 s electing the t ransmit u ser c ell f ilter a ction the transmit atm cell processor block permits the user to specify the action that the user cell filter will take on each cell, that meets certain ?user-defined? filter ing requirements. the user can accomplish this by setting bits 2 (copy cell enable) and 1 (discard cell enable) , within the transmit atm filter control ? byte 0? register; to the appropriate values. th ese two bit-fields are highlighted below. transmit atm filter # 0, # 1, # 2, # 3 control ? byte 0 (address = 0xnf43, 0xnf53, 0xnf63, 0xnf73) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused user cell filter enable copy cell enable discard cell enable user cell filter sense r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 1 x x x bit 2 ? copy cell enable this bit-field permits the user to configure the ?tra nsmit user cell? filter (within the transmit atm cell processor block) to either replicate (copy) or not re plicate a given cell that complies with the ?user-defined? filtering requirements. all copied ce lls are routed to the ?transmit at m cell processor extraction memory?, where their contents can be read out by the user via the microprocessor interface. setting this bit-field to ?1? configures the transmit user cell filter to copy all cells that comply with the ?user- cell? filter requirements, and to route these cells to the ?transmit atm cell processor ? extraction memory?. conversely, setting this bit-field to ?0? configures the tr ansmit user cell filter to not copy these cells, and not route these cells to the ?transmit atm cell processor ? extraction memory.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 182 bit 1 ? discard cell enable this bit-field permits the user to configures the ?tr ansmit user cell? filter (w ithin the transmit atm cell processor block) either discard or not discard a giv en cell that complies with t he ?user-defined? filtering requirements. cells that are discarded will not be rout ed to the ?transmit sts-3c poh processor? block. cells that are not discarded will proceed on through the remainder of the transmit atm cell processor block circuitry, for further processing. setting this bit-field to ?1? configures the transmit user cell filter to discard all cells that comply with the ?user-cell? filter requirements. conversely, setting this bit-field to ?0? configures the tr ansmit user cell filter to not discard the cells that comply with the ?user-cell? filter requirements. 2.2.6.3 d efining the u ser c ell f ilter s ense the sense of a given transmit user cell filter is defined by the state of bit 0 (user cell filter sense) within the ?transmit atm filter control ? byte 0? register; as described below. bit 0 - user cell filter sense transmit atm filter # 0 , # 1, # 2, # 3 control ? byte 0 (address = 0xnf43, 0xnf53, 0xnf63, 0xnf73) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused user cell filter enable copy cell enable discard cell enable user cell filter sense r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 1 x x x this bit-field controls the ?filter mode?. if the user sets this bit-field to ?1? then the ?transmit user-cell? filter will act, per the settings within bits 2 (copy cell enable) and 1 (discard cell enable) on cells with header byte patterns matching the ?user-cell? filtering criteria. c onversely, setting this bit-field to ?0? configures the ?transmit user-cell? filter to act, per the settings with in bits 2 (copy cell enable) and 1 (discard cell enable) on cells with header byte patterns not mat ching the ?user-cell? filtering criteria. 2.2.6.4 s pecifying the t ransmit u ser c ell f iltering c riteria as described above, each of the four transmit user cell filters (within the transmit atm cell processor block) can be configured to perform a variety of ac tions (e.g., copy cells, discard cells, etc); based upon whether the header byte patterns of user cells mat ch; or do not match a pa rticular ?user-defined? filter criteria. the ?user-defined? filter criter ia (for each of the four transmit user cell filter blocks, within the transmit atm cell processor block) are ultimately defined by the va lues residing within a total of eight (8) registers. four of these registers are referred to as ?user cell filter ? pattern? registers; and the remaining four registers are referred to as ?user cell filter ? check? registers. each of these register types are defined below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 183 2.2.6.5 t ransmit u ser c ell f ilter ? p attern r egisters the four user cell filter ? pattern registers permit the user to specify the header byte pattern for the transmit user cell filter. there are four user cell filt er ? pattern registers (one for each of the four (4) header bytes, within an atm cell). the bit-format of t hese ?user cell filter ? pattern registers? is presented below. transmit atm filter # 0, # 1, # 2, # 3 pattern ? header byte 1 (address = 0xnf44, 0xnf54, 0xnf64, 0xnf74) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter pattern ? header byte 1[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 transmit atm filter # 0, # 1, # 2, # 3 pattern ? header byte 2 (address = 0xnf45, 0xnf55, 0xnf65, 0xnf75) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter pattern ? header byte 2[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 transmit atm filter # 0, # 1, # 2, # 3 pattern ? header byte 3 (address = 0xnf46, 0xnf56, 0xnf66, 0xnf76) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter pattern ? header byte 3[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 transmit atm filter # 0, # 1, # 2, # 3 pattern ? header byte 4 (address = 0xnf47, 0xnf57, 0xnf67, 0xnf77) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter pattern ? header byte 4[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 note: each of the four transmit user cell filters (within the tr ansmit atm cell processor block) contains their own set of ?user cell filter ? pattern? registers.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 184 2.2.6.6 t ransmit u ser c ell f ilter ? c heck r egisters the four user cell filter ? check registers permit the us er to specify which bits (within the header bytes of user cells) will be checked and comp ared with the contents of the ?user cell filter ? pattern registers?. there are four (4) ?user cell filter-check? registers (one for each of the four header bytes within an atm cell). setting a particular bit-field to ?0? configures the ?transmit user cell filter? to not compare the corresponding bit-field (within the header bytes of the incoming user cell) to the corresponding bit-value, within the user cell filter ? pattern register; during user cell pattern checking. conversely, setting a particular bit-field to ?1? configures the ?transmit user cell filter? to compare the corresponding bit-field (within the header bytes of the incoming user cell) to t he corresponding bit-value, within the user cell filter ? pattern register; during user cell pattern checking. for example, if the user were write the value ?0x00? in to a given ?user cell filter ? check register?, then the transmit user cell filter will not check and compare t he value of the corresponding header byte, within an incoming user cell; to the contents of the corresponding ?u ser cell filter ? pattern? register during user cell pattern checking. conversely, if the user were to writ e the value ?0xff? into a given ?user cell filter ? check register?, then the user cell filter will check and compare all eight bits (within the corresponding byte) within an incoming user cell; to the content s of the corresponding ?user cell filter ? pattern? register during user cell pattern checking. the bit-format of the four ?user cell filt er ? check registers? is presented below. transmit atm filter # 0, # 1, # 2, # 3 check ? header byte 1 (address = 0xnf48, 0xnf58, 0xnf68, 0xnf78) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter check ? header byte 1[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 transmit atm filter # 0, # 1, # 2, # 3 check ? header byte 2 (address = 0xnf49, 0xnf59, 0xnf69, 0xnf79) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter check ? header byte 2[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 transmit atm filter # 0, # 1, # 2, # 3 check ? header byte 3 (address = 0xnf4a, 0xnf5a, 0xnf6a, 0xnf7a) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter check ? header byte 3[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 185 transmit atm filter # 0, # 1, # 2, # 3 check ? header byte 4 (address = 0xnf4b, 0xnf5b, 0xnf6b, 0xnf7b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter check ? header byte 4[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 note: each of the four user cell filters (within the transmit at m cell processor block) contains their own set of ?user cell filter ? check? registers. 2.2.6.7 c ounting f iltered c ells the user can keep account of the number of user cells that have been filtered out by the transmit user cell filter by periodically reading out the contents of the ?transmit atm filter co unt? registers. each time a user cell is filtered (e.g., either discarded or copied) by the ?transmit user cell? filter, then this counter will be incremented by the value of ?1?. this counter will increment until it reaches the value of 0xffffffff. at this time, the counter will ?saturate? and will not increment any further until read. these registers are 32 bits, in width and are ?reset-upon-read. the bi t-format for these regi sters (for each of t he four filters) is presented below. transmit atm filter # 0, # 1, # 2, # 3 ? filtered cell counter ? byte 3 (address = 0xnf4c, 0xnf5c, 0xnf6c, 0xnf7c) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 filtered cell count[31:24] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 transmit atm filter # 0, # 1, # 2, # 3 ? filtered cell counter ? byte 2 (address = 0xnf4d, 0xnf5d, 0xnf6d, 0xnf7d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 filtered cell count[23:16] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 transmit atm filter # 0, # 1, # 2, # 3 ? filter ed cell counter ? byte 1 (address = 0xnf4e, 0xnf5e, 0xnf6e, 0xnf7e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 filtered cell count[15:8] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 186 transmit atm filter # 0, # 1, # 2, # 3 ? filtered cell counter ? byte 0 (address = 0xnf4f, 0xnf5f, 0xnf6f, 0xnf7f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 filtered cell count[7:0] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 note: each of the four user cell filters (within the transmit atm cell processor block) contains their own set of ?filtered cell counter? registers. the procedure for reading out the contents of the transmit atm filter ? filtered cell counter register in order to properly read out the contents of these r egisters, the user must read these registers in the following order. ? transmit atm filter #0, #1, #2, #3 ? filtered ce ll counter ? byte 3 (address = 0xnf4c, 0xnf5c, 0xnf6c, 0xnf7c) ? transmit atm filter #0, #1, #2, #3 ? filtered ce ll counter ? byte 2 (address = 0xnf4d, 0xnf5d, 0xnf6d, 0xnf7d) ? transmit atm filter #0, #1, #2, #3 ? filtered ce ll counter ? byte 1 (address = 0xnf4e, 0xnf5e, 0xnf6e, 0xnf7e) ? transmit atm filter #0, #1, #2, #3 ? filtered cell counter ? byte 0 (address = 0xnf4f, 0xnf5f, 0xnf6f, 0xnf7f)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 187 2.2.6.8 t he t ransmit c ell i nsertion b uffer /p rocessor the transmit atm cell processor block consists of a ?transmit cell insertion buffer/processor? block. figure 24 presents the functional block diagram of the transmit atm cell processor block with the ?transmit cell insertion buffer/processor? block highlighted. figure 24: illustration of the transmit atm cell pro cessor block functi onal block diagram, with the ?transmit cell insertion buffer/processor? block highlighted parity checker block parity checker block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte calculation & insertion block hec byte calculation & insertion block cell payload scrambler block cell payload scrambler block txfifo txfifo transmit utopia interface block microprocessor interface block microprocessor interface block idle cell generator idle cell generator main data path to transmit sonet/sts-3c poh processor block transmit gfc nibble-field input port block transmit gfc nibble-field input port block txgfc input port the transmit cell insertion buffer/processor block permi ts the user to load the contents of an ?outbound? atm cell into the ?transmit cell insertion buffer? via t he microprocessor interface. once this cell has been loaded into the ?transmit cell insertion buffer?, then it will be transmitted to the remote terminal equipment (via the transmit data path) whenever the ?txfifo? (wit hin the transmit utopia interface block) is depleted of user cells. an example of an application where this feature would be useful is in the loading and transmission of oam cells. the format of atm cell data that is writte n into the ?transmit cell insertion? buffer as the user loads the contents of an atm cell into the ?transmit cell insertion? buffer (via the microprocessor interface), they will be expected to writ e this atm cell data into a 32 bit wide register/buffer interface. as a consequence, the user must write in 56-byte size at m cells into the ?transmit cell insertion? buffer. the byte format of this 56 byte atm cell is as illustrated below in figure 25.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 188 figure 25: byte-format of the atm cell that is to be loaded into the ?transmit cell insertion? memory header bytes (4 bytes) hec byte (1 byte) user defined field (3 bytes) cell payload bytes (48 bytes) as a consequence, the user must write in a total of 14 ? 32-bit words? into the ?trans mit cell insertion? buffer for each atm cell that is written into the ?transmit cell insertion? buffer. procedure for writing a cell into the ?transmit cell insertion buffer? the user can write an atm cell into the ?transmit ce ll insertion buffer? with in the transmit atm cell processor block, by exec uting the following steps. step 1 ? flush the contents of the ?transmit cell insertion buffer? this is accomplished by executing a ?transmit cell insertion buffer? reset. the user can perform this ?transmit cell insertion buffer? reset by doing the following. step 1a ? write a ?0? into bit 2 (insertion memory reset*), within the ?transmit atm cell ? memory control? register; as depicted below. transmit atm cell ? memory control register (address = 0xnf13) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1 0 1->0 1 0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 189 step 1b ? write a ?1? into bit 2 (insertion memory reset*), within the ?transmit atm cell ? memory control? register; as depicted below. transmit atm cell ? memory control register (address = 0xnf13) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1 0 0->1 1 0 note: this step should typically be performed upon power-up, pr ior to writing in any atm cell data into the ?transmit cell insertion buffer?. this step is not necessary afte r the first cell has been written into the ?transmit cell insertion buffer? following a power cycle to the chip. step 2 ? check and verify that there is sufficient space available (within the transmit cell insertion buffer) to handle this cell. this can be accomplished by one of two approaches. ? polling approach ? interrupt-driven approach. each of these approaches is described below. executing step 2 using the polling approach the user can determine whether or not there is room (t o write another atm cell of data) in to the ?transmit cell insertion? buffer? by polling the state of bit 1 (ins ertion memory room) within the ?transmit atm cell ? memory control register? as depicted below. transmit atm cell ? memory control register (address = 0xnf13) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1 0 1 x 0 if bit 1 (insertion memory room) is set to ?1? then the ?transmit cell insertion buffer? is not too full to accept another cell. at this point, the microprocessor can now move onto step 3. conversely, if bit 1 is set to ?0? then the ?transmit cell insertion buffer? is to o full to accept another cell. the microprocessor interface should continue to poll the state of this bit-fiel d and wait until this bit-field toggles to ?1?. executing step 2 using the interrupt-driven approach in order to reduce or eliminate the microprocessor overhea d of continuously polling the state of bit 1, the user can use the ?transmit cell insertion? interrupt feature, within the chip. if the mi croprocessor invokes this feature, then the xrt94l33 will generate an interrupt any time a cell (residing in the transmit cell insertion buffer) has been inserted into the ?transmit output data path? (thereby freeing up some space within the transmit cell insertion buffer).
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 190 the user can enable the ?transmit cell insertion? interr upt by setting bit 4 (cell insertion interrupt enable), within the ?transmit atm cell processor ? interrupt enable? register to ?1? as indicated below. transmit atm cell processor ? interrupt enable register (address = 0xnf0f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt enable cell insertion interrupt enable cell extraction memory overflow interrupt enable cell insertion memory overflow interrupt enable detection of hec byte error interrupt enable detection of parity error interrupt enable r/o r/o r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 0 once a cell (residing within the transmit cell insertion buffer) has been inserted into the ?transmit output data path?, then the xrt94l33 will do all of the following: ? it will toggle the ?int*? output pin ?low?. ? it will set bit 4 (cell insertion in terrupt status), within the transmit atm cell proces sor ? interrupt status register; to ?1? as depicted below. transmit atm cell processor ? interrupt status register (address = 0xnf0b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt status cell insertion interrupt status cell extraction memory overflow interrupt status cell insertion memory overflow interrupt status detection of hec byte error interrupt status detection of parity error interrupt status r/o r/o rur rur rur rur rur rur 0 0 0 1 0 0 0 0 at this point, the user can now proceed on with step 3. step 3 ? inform the ?transmit cell insertion processor? that the very next 32-bit word to be written into the ?transmit cell insertion buffer? is the first word of a new atm cell. this is accomplished by writing the value ?1? into bit 0 (insertion memory write soc), within the ?transmit atm cell ? memory control r egister? as depicted below. transmit atm cell ? memory control register (address = 0xnf13) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1 0 1 1 1
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 191 step 4 ? write the very first 32-bit word of this ne w atm cell into the ?transmit cell insertion buffer?. this is accomplished by executin g the following four sub-steps. step 4a - write the contents of first byte (of this new atm cell) into the transmit atm cell ? insertion/extraction memory register ? byte 3; as depicted below. transmit atm cell ? insertion/extraction memory register ? byte 3 (address = 0xnf14) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[31:24] r/w r/w r/w r/w r/w r/w r/w r/w a7 a6 a5 a4 a3 a2 a1 a0 note: in this case, the contents of the first byte (within this atm cell) is of the value [a7, a6, a5, a4, a3, a2, a1, a0] step 4b ? write the contents of the second byte (of this new atm cell) into the transmit atm cell ? insertion/extraction memory register ? byte 2; as depicted below. transmit atm cell ? insertion/extraction memory register ? byte 2 (address = 0xnf15) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[23:16] r/w r/w r/w r/w r/w r/w r/w r/w b7 b6 b5 b4 b3 b2 b1 b0 note: in this case, the contents of the second byte (within this atm cell) is of the value [b7, b6, b5, b4, b3 , b2, b1, b0] step 4c ? write the contents of the third byte (of this new atm cell) into the transmit atm cell ? insertion/extraction memory register ? byte 1; as depicted below. transmit atm cell ? insertion/extraction memory register ? byte 2 (address = 0xnf16) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[15:8] r/w r/w r/w r/w r/w r/w r/w r/w c7 c6 c5 c4 c3 c2 c1 c0 note: in this case, the contents of the second byte (within this atm cell) is of the value [c7, c6, c5, c4, c3, c2, c1, c0]
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 192 step 4d ? write the contents of the fourth byte (of this new atm cell) into the transmit atm cell ? insertion/extraction memory register ? byte 0; as depicted below. transmit atm cell ? insertion/extraction memory register ? byte 2 (address = 0xnf17) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[7:0] r/w r/w r/w r/w r/w r/w r/w r/w d7 d6 d5 d4 d3 d2 d1 d0 note: in this case, the contents of the second byte (within this atm cell) is of the value [d7, d6, d5, d4, d3, d2, d1, d0] step 5 ? inform the ?cell insertion processor? that the very next 32-bit word to be written into the ?cell insertion buffer? is not th e first word of a new atm cell. this is accomplished by writing the value ?0? into bit 0 (insertion memory write soc), within the ?transmit atm cell ? memory control r egister? as depicted below. transmit atm cell ? memory control register (address = 0xnf13) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1 0 1 1 0 step 6 ? continue to write the contents of the remain ing bytes of this atm cell into the ?cell insertion memory?. this is accomplished by executing the procedur e, outlined in step 4, repeatedly for 13 times. notes: as the user writes the contents of an atm cell into t he ?transmit cell insertion memory? they must follow the mandated atm cell byte format, as depicted in 1. . 2. if the user performs a read operation to the ?transmit atm cell ? insertion/extraction memory register ? bytes 3 through 0? they will not be readi ng out the contents of t he transmit cell insertion buffer. instead, the user will be reading out dat a from the ?transmit cell extraction? buffer.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 193 2.2.6.9 t he t ransmit c ell e xtraction b uffer /p rocessor the transmit atm cell processor block consists of a ?transmit cell extraction buffer/processor? block. figure 26 presents the functional block diagram of the ?transmit atm cell processor block with the ?transmit cell extraction buffer/processor? block highlighted. figure 26: illustration of the transmit atm cell pro cessor block functi onal block diagram, with the ?transmit cell extraction buffer/processor? block highlighted parity checker block parity checker block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte calculation & insertion block hec byte calculation & insertion block cell payload scrambler block cell payload scrambler block txfifo txfifo transmit utopia interface block microprocessor interface block microprocessor interface block idle cell generator idle cell generator main data path to transmit sonet/sts-3c poh processor block transmit gfc nibble-field input port block transmit gfc nibble-field input port block txgfc input port the transmit cell extraction buffer/processor block permits the user to read out the contents of an ?inbound? atm cell via the microprocessor interface. if the user configures the ?transmit user cell filter? appropriately, the ?transmit user cell filter? will copy (e.g., replicate) the contents of certain cells (which comply with the user cell filtering requirements). these copied cells will be routed to the ?transmit cell extraction buffer/processor? block where it can be read out and processed by the microprocessor interface.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 194 the format of the atm cell that is read fr om the ?transmit cell extraction? buffer as the user reads out the contents of an atm cell fr om the ?transmit cell extr action? buffer (via the microprocessor interface), they will be expected to read this atm cell data via a 32-bit wide register/buffer interface. as a consequence, the user must read out 56 byte size atm cells from the ?transmit cell extraction? buffer. the byte format of th is 56-byte atm cell is as illustrated below. figure 27: byte format of the atm cells that are read out from the ?transmit cell extraction? memory header bytes (4 bytes) hec byte (1 byte) user defined field (3 bytes) cell payload bytes (48 bytes) as a consequence, the user must read out a total of 14 ?32-bit? words from the ?transmit cell extraction? buffer for each atm cell that is read out of the transmit cell extraction buffer. procedure for reading a cell from the ?transmit cell extraction buffer? the user can read an atm cell from the ?transmit cell extraction buffer? within the transmit atm cell processor block, by exec uting the following steps. step 1 ? flush the contents of the ?transmit cell extraction buffer? this is accomplished by executing a ?transmit cell extraction buffer? reset. the user can perform this ?cell extraction buffer? reset by doing the following.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 195 step 1a ? write a ?0? into bit 4 (extraction memory reset*) within the ?transmit atm cell ? memory control? register; as depicted below. transmit atm cell ? memory control register (address = 0xnf13) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1->0 0 1 1 0 step 1b ? write a ?1? into bit 4 (extraction memory reset *), within the ?transmit atm cell ? memory control? register; as depicted below. transmit atm cell ? memory control register (address = 0xnf13) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0->1 0 1 1 0 note: this step should typically be performed upon power-up, prior to processing any atm cell traffic through the xrt94l33. this step is not necessary after the first cell has been read from the ?transmit cell extraction buffer? following a pow er cycle to the chip. step 2 ? check and see if an atm cell exists in the ?transmit cell extraction buffer? this can be accomplished by one of two approaches. ? polling approach ? interrupt-driven approach each of these approaches is described below. executing step 2 using the polling approach the user can determine whether or not a cell is avail able, within the ?transmit cell extraction buffer? by testing the state of bit 3 (extraction memory clav) wi thin the transmit atm cell ? memory control register; as depicted below. transmit atm cell ? memory control register (address = 0xnf13) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1 x 1 1 0 if bit 3 is set to ?1?, then the ?transmit cell extracti on buffer? contains an atm cell that needs to be read. at this point, the user should proceed on to step 3.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 196 conversely, if bit 3 is set to ?0?, then the ?transmit cell extraction buffe r? does not contain an atm cell that needs to be read. at this point, the microprocessor interf ace should continue to poll the state of this bit-field and wait until this bit-field toggles to ?1?. executing step 2 using the interrupt-driven approach in order to reduce or eliminate the microprocessor overhea d of continuously polling the state of bit 3, the user can use the ?transmit cell extraction? interrupt feature, within the chip. if the microprocessor invokes this feature, then the xrt94l33 will generate an interrupt anytime a new cell has been received and loaded into the ?transmit cell extraction buffer?. the user can enable the ?cell extraction? interrupt by setti ng bit 5 (cell extraction interrupt enable), within the ?transmit atm cell processor ? interrupt enable? register to ?1? as indicated below. transmit atm cell processor ? interrupt enable register (address = 0xnf0f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt enable cell insertion interrupt enable cell extraction memory overflow interrupt enable cell insertion memory overflow interrupt enable detection of hec byte error interrupt enable detection of parity error interrupt enable r/o r/o r/w r/w r/w r/w r/w r/w 0 0 1 0 0 0 0 0 once the ?cell extraction buffer? receives a ?copied? cell from the ?transmit user cell filter?, then the xrt94l33 will do all of the following: ? it will toggle the ?int*? output pin ?low?. ? it will set bit 5 (cell extraction interrupt status) within the transmit atm cell processor ? interrupt status register, to ?1? as depicted below. transmit atm cell processor ? interrupt status register (address = 0xnf0b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt status cell insertion interrupt status cell extraction memory overflow interrupt status cell insertion memory overflow interrupt status detection of hec byte error interrupt status detection of parity error interrupt status r/o r/o rur rur rur rur rur rur 0 0 1 0 0 0 0 0 at this point, the user can now proceed onto step 3. step 3 ? read out the very first 32-bit word of this new atm cell from the ?transmit cell extraction buffer?. this is accomplished by executin g the following four sub-steps. step 3a ? read the contents of the first byte (of this newly received atm cell) from the ?transmit atm cell ? insertion/extraction memory register ? byte 3; as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 197 transmit atm cell ? insertion/extraction memory register ? byte 3 (address = 0xnf14) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[31:24] r/w r/w r/w r/w r/w r/w r/w r/w a7 a6 a5 a4 a3 a2 a1 a0 note: in this case, the contents of the first byte (within this atm cell) is of the value [a7, a6, a5, a4, a3, a2, a1, a0] step 3b ? read the contents of the second byte (of this new atm cell) from the transmit atm cell ? insertion/extraction memory register ? byte 2; as depicted below. transmit atm cell ? insertion/extraction memory register ? byte 2 (address = 0xnf15) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[23:16] r/w r/w r/w r/w r/w r/w r/w r/w b7 b6 b5 b4 b3 b2 b1 b0 note: in this case, the contents of the second byte (within this atm cell) is of the value [b7, b6, b5, b4, b3 , b2, b1, b0] step 3c ? read the contents of the third byte (of this new atm cell) from the transmit atm cell ? insertion/extraction memory register ? byte 1; as depicted below. transmit atm cell ? insertion/extraction memory register ? byte 2 (address = 0xnf16) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[15:8] r/w r/w r/w r/w r/w r/w r/w r/w c7 c6 c5 c4 c3 c2 c1 c0 note: in this case, the contents of the second byte (within this atm cell) is of the value [c7, c6, c5, c4, c3, c2, c1, c0] step 3d ? read the contents of the fourth byte (of this new atm cell) from the transmit atm cell ? insertion/extraction memory register ? byte 0; as depicted below. transmit atm cell ? insertion/extraction memory register ? byte 2 (address = 0xnf17) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[7:0] r/w r/w r/w r/w r/w r/w r/w r/w d7 d6 d5 d4 d3 d2 d1 d0 note: in this case, the contents of the second byte (within this atm cell) is of the value [d7, d6, d5, d4, d3, d2, d1, d0] step 4 ? continue to read out the contents of the remaining bytes of this atm cell from the ?transmit cell extraction memory?. this is accomplished by executin g the procedure, outlined in step 3, repeatedly for 13 more times.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 198 2.2.6.10 t he i dle c ell g enerator the transmit atm cell processor block consists of a ?idle cell generator? block. figure 28 presents the functional block diagram of the ?transmit atm cell processor block with the ?idle cell generator? block highlighted. figure 28: illustration of the transmit atm cell pro cessor block functi onal block diagram, with the ?idle cell generator? block highlighted parity checker block parity checker block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte calculation & insertion block hec byte calculation & insertion block cell payload scrambler block cell payload scrambler block txfifo txfifo transmit utopia interface block microprocessor interface block microprocessor interface block idle cell generator idle cell generator main data path to transmit sonet/sts-3c poh processor block transmit gfc nibble-field input port block transmit gfc nibble-field input port block txgfc input port whenever the txfifo (within the transmit utopia in terface block) does not contain a complete cell, the transmit atm cell processor will firs t read out any atm cell data that resides within the ?transmit cell insertion buffer? and will insert this (or these) atm cells into the ?transmit data path?. once both the ?txfifo? and the ?transmit cell insertion buffer? are depleted, then the transmit atm cell processor block will automatically fill in the sts-3 spe bandwidth by generating and transmitting idle cells via the ?transmit data path?. by default, the transmit atm cell processo r block will generate idle ce lls that contain header byte patterns which conform to the atm forum recommendations. however, the xrt94l33 does contain some registers that permit the user to ?customize? the header byte and payload byte pattern of these idle cells. the procedure for configuring the idle cell generator to generate and transmit idle cells with ?customized? header and payload bytes is presented below. the procedure for configuring the transmit atm cell processor block to transmit idle cells with ?user-specified? header and payload bytes the user can configure the transmit atm cell processor block to generate and transmit idle cells with ?user- specified? header and payload bytes, by executing the following steps.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 199 step 1 ? write the ?desired value? for header byte 1 (within these idle cells) into the ?transmit atm cell ? idle cell header byte 1 register; as depicted below. transmit atm cell ? idle cell header byte 1 register (address = 0xnf18) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 idle_cell_header_byte_1[7:0] r/w r/w r/w r/w r/w r/w r/w r/w a7 a6 a5 a4 a3 a2 a1 a0 step 2 ? write the ?desired value? for header byte 2 (within these idle cells) into the ?transmit atm cell ? idle cell header byte 2 register; as depicted below. transmit atm cell ? idle cell header byte 2 register (address = 0xnf19) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 idle_cell_header_byte_2[7:0] r/w r/w r/w r/w r/w r/w r/w r/w b7 b6 b5 b4 b3 b2 b1 b0 step 3 ? write the ?desired value? for header byte 3 (within these idle cells) into the ?transmit atm cell ? idle cell header byte 3 register; as depicted below. transmit atm cell ? idle cell header byte 3 register (address = 0xnf1a) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 idle_cell_header_byte_3[7:0] r/w r/w r/w r/w r/w r/w r/w r/w c7 c6 c5 c4 c3 c2 c1 c0 step 4 ? write the ?desired value? for header byte 4 (within these idle cells) into the ?transmit atm cell ? idle cell header byte 4 register; as depicted below. transmit atm cell ? idle cell header byte 4 register (address = 0xnf1b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 idle_cell_header_byte_4[7:0] r/w r/w r/w r/w r/w r/w r/w r/w d7 d6 d5 d4 d3 d2 d1 d0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 200 step 5 ? write the ?desired value? for the payload byte (within these idle cells) into the ?transmit atm cell ? idle cell payload byte register; as depicted below. transmit atm cell ? idle cell payload byte register (address = 0xnf1f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 idle_cell_payload_byte[7:0] r/w r/w r/w r/w r/w r/w r/w r/w p7 p6 p5 p4 p3 p2 p1 p0 note: each of the 48 bytes, within the idle cell payload w ill be set to the value written into this register. 2.2.6.11 t he t ransmit gfc n ibble -f ield s erial i nput p ort the transmit atm cell processor block consists of a ?transmit gfc nibble-field? input port. figure 29 presents the functional block diagram of the ?transmi t atm cell processor? block with the ?transmit gfc nibble-field serial input port? block highlighted. figure 29: an illustration of the functional block di agram of the transmit atm cell processor block, with the ?transmit gfc nibble-field se rial input port? block highlighted parity checker block parity checker block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte calculation & insertion block hec byte calculation & insertion block cell payload scrambler block cell payload scrambler block txfifo txfifo transmit utopia interface block microprocessor interface block microprocessor interface block idle cell generator idle cell generator main data path to transmit sts-3c/sts-12c poh processor block transmit gfc nibble-field input port block transmit gfc nibble-field input port block txgfc input port as the name of this port implies, this port permits the us er to insert his/her value for the gfc nibble into each outbound atm cell.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 201 figure 30: behavior of txgfc, txgfcclk, and txgfcmsb during gfc insertion into the ?outbound? txgfcclk txgfcmsb t14 txgfc t16 bit 3 bit 2 bit 1 bit 0 t17 t13 t15 2.2.6.12 t he hec b yte c alculation and i nsertion b lock the transmit atm cell processor block consists of a ?hec byte calculation and insertion? block. figure 31 presents the functional block diagram of the ?trans mit atm cell processor? block with the ?hec byte calculation and insertion? block highlighted. figure 31: illustration of the tran smit atm cell processor block fun ctional block diagram with the hec byte calculator and insertion? block highlighted parity checker block parity checker block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte calculation & insertion block hec byte calculation & insertion block cell payload scrambler block cell payload scrambler block txfifo txfifo transmit utopia interface block microprocessor interface block microprocessor interface block idle cell generator idle cell generator main data path to transmit sonet/sts-3c poh processor block transmit gfc nibble-field input port block transmit gfc nibble-field input port block txgfc input port
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 202 the ?hec byte calculation & insertion? block receives either filtered user cells or idle cells from the upstream circuitry, within the transmit atm cell processor block. as it receives these cells, the ?hec byte calculation & insertion? block can be configured to perform any of the following actions on these cells. ? to compute and verify the hec bytes of incoming cells from upstream circuitry within the transmit atm cell processor block ? to regenerate the hec byte (e.g., to comput e and insert the hec bytes of incoming cells) ? to add the coset polynomial to the hec byte, prior to transmission via the ?transmit data path? ? a detailed description of the hec byte calcul ation & insertion block is presented below. computing and verifying hec bytes of incoming cells as the hec byte calculation & insertion block receives at m cells, it takes the first four bytes of each cell and computes a crc-8 value via the generating polynomial x 8 + x 2 + x + 1. note: the user has the option to have the coset polynomial x 6 + x 4 + x 2 + 1 modulo-2 added to the crc-8 byte and, insert this newly modified crc-8 value into the fifth octet position within the cell before transmission. this option will be discussed later in this section. configuring the hec byte calculation & inser tion block to check for hec byte errors if the user wishes to configure the transmit atm cell processor block to compute, verify and flag hec byte errors in cells originating from upstream circuitry, then they must write a ?1? into bit 6 (hec byte check enable) within the ?transmit atm control ? byte 0, as depicted below. transmit atm control ? byte 0 (address = 0xnf03) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 hec byte invert hec byte check enable parity check enable discard cell upon parity error odd parity unused cell payload scramble enable r/w r/w r/w r/w r/w r/o r/o r/w 0 1 0 x x 0 0 x if the user implements this configuration option, then t he hec byte calculation & insertion block will compute and verify the hec byte, within all atm cells that it re ceives from the idle cell generator and the transmit user cell filter blocks. if the hec byte calculation & insertion block detects a hec byte error, then the transmit atm cell processor block will generate the ?detection of hec byte error? interrupt. the transmit atm cell processor block will indicate that it is generat ing this interrupt by doing all of the following. ? it will toggle the ?int*? output pin ?low?. ? the transmit atm cell processor block will set bit 1 (detection of hec byte error interrupt status), within the ?transmit atm cell processor ? interrupt status register? as depicted below. transmit atm cell processor ? interrupt status register (address = 0xnf0b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt status cell insertion interrupt status cell extraction memory overflow interrupt status cell insertion memory overflow interrupt status detection of hec byte error interrupt status detection of parity error interrupt status r/o r/o rur rur rur rur rur rur
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 203 0 0 0 0 0 0 1 0 ? finally, the transmit atm cell processor block will increment the ?transmit atm cell ? hec byte error count? register. the ?t ransmit atm cell? hec byte error count register is a 32-bit ?reset-upon- read? register. the bit-format for this register is presented below. transmit atm cell ? hec byte error count register ? byte 3 (address = 0xnf30) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_hec_byte_error_count[31:24] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 transmit atm cell ? hec byte error count register ? byte 2 (address = 0xnf31) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_hec_byte_error_count[23:16] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 transmit atm cell ? hec byte error count register ? byte 1 (address = 0xnf32) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_hec_byte_error_count[15:8] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 transmit atm cell ? hec byte error count register ? byte 0 (address = 0xnf33) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_hec_byte_error_count[7:0] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 in general, if the hec byte calculation & insertion block detects atm cells that contains ?single-bit? or ?multi- bit? errors (within the header bytes), then it will not co rrect these header byte erro rs. further, the transmit atm cell processor block will automati cally discard these erred cells un less it has been configured to recalculate and insert a new hec byte into the 5 th octet position of each atm cell (as discussed below in section 4.2.2.7.2). note: the transmit atm cell ? hec byte error count register will be incremented by the value ?1? each time the transmit atm cell processor detects a hec byte error in the incoming atm cell stream. this 32-bit register will continue to be incremented until it reaches the va lue ?0xffffffff?. at this point, this reset-upon-read register will saturate and will not increment any further , until the microprocessor reads out the contents of these registers. if the user does not wish to configure the ?hec byte calculation & insertion? block to check for hec byte errors in the incoming atm cell data-stream, then they should set bit 6 (hec byte check enable), within the transmit atm control ? byte 0 register to ?0? as indicated below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 204 transmit atm control ? byte 0 (address = 0xnf03) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 hec byte invert hec byte check enable parity check enable discard cell upon parity error odd parity unused cell payload scramble enable r/w r/w r/w r/w r/w r/o r/o r/w 0 0 0 x x 0 0 x in this mode, all atm cells (even those with hec byte errors) will pass through the ?hec byte calculation & insertion? block, without any flagging of hec byte errors. configuring the hec byte calculation & insertion bl ock to regenerate (e.g., recompute and insert) the hec byte, prior to transmission via the ?transmit data path? in addition to being capable of detecting and flagging hec byte errors, the ?hec byte calculation & insertion? block can be configured to recompute and insert a new hec byte into the fifth octet position within all atm cells that are processed by the ?hec byte calculati on & insertion? block. the user can implement this configuration by writing a ?1? into bit 0 (re-calculat e hec byte enable), within the ?transmit atm control ? byte 1? register, as depicted below. transmit atm control ? byte 1 (address = 0xnf02) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 test cell mode enable test cell generator ? one shot gfc_enable[3:0] coset addition re- calculate hec byte enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 1 notes: setting this bit-field to ?1? configures the ?hec byte calculation & insertion? block to unconditionally compute a new hec byte (based upon the value of the first four header bytes of a given atm cell) and insert this value into the 5 th octet position within each outbound atm cell. further, this configuration setting also configures the ?hec byte calculation & insertion? block to not discard any atm cells that it receives from upstream circuitry, even those cells that it determines to contain hec byte errors. this bit-field is ignored if bit 6 (hec byte check enable) wi thin the ?transmit atm control ? byte 0? register (address = 0xnf03) is set to ?0?. other options available via the ?hec byte calculation & insertion? block the user has the following additional options via the ?hec byte calculation & insertion? block. ? to modulo-2 add the coset polynomial to the hec byte, prior to transmission. ? to invert the hec byte each of these options is discussed below. adding the coset polynomial to the hec byte the ?hec byte calculation & insertion? block permit s the user to configure it to modulo-2 add the coset polynomal (e.g., x 6 + x 4 + x 2 + 1) to the crc-8 value (e.g., the hec by te). afterwards, this ?newly computed? hec byte would be written back into the fifth oc tet position within each outbound atm cell.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 205 the user can implement this configuration option by wr iting a ?1? into bit 1 (coset addition) within the ?transmit atm control ? byte 1? register, as depicted below. transmit atm control ? byte 1 (address = 0xnf02) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 test cell mode enable test cell generator ? one shot gfc_enable[3:0] coset addition re- calculate hec byte enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 1 1 note: in order to configure the ?hec byte calculation & inserti on? block to add the coset po lynomial to the hec byte, it is imperative that the user also set bit 0 (re-calculate hec byte enable), within the same register; to ?1? as depicted above. inverting the hec byte the ?hec byte calculation & insertion? block permits the us er to configure it to invert the value of each of the eight bits within the hec byte of each outbound atm cell. the user can implement this configuration option by executing the following steps. step 1 ? configure the ?hec byte calculation & insertion? block to compute and insert the hec byte into the fifth octet position, within each ?outbound? atm cell. this is accomplished by setting bit 0 (re-calculate hec byte enable), within the ?transmit atm control ? byte 1? register to ?1?, as depicted below. transmit atm control ? byte 1 (address = 0xnf02) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 test cell mode enable test cell generator ? one shot gfc_enable[3:0] coset addition re- calculate hec byte enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 x 1 step 2 ? configure the ?hec calculation & insertion? block to now invert the contents of the hec byte that it is computing. this is accomplished by setting bit 7 (hec byte invert), within the ?transmit atm control ? byte 0? register to ?1? as depicted below. transmit atm control ? byte 0 (address = 0xnf03) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 hec byte invert hec byte check enable parity check enable discard cell upon parity error odd parity unused cell payload scramble enable r/w r/w r/w r/w r/w r/o r/o r/w 1 0 0 x x 0 0 x
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 206 2.2.6.13 t he c ell p ayload s crambler b lock the transmit atm cell processor block consists of a ?cell scrambler? block. figure 32 presents the functional block diagram of the ?transmit atm cell processor block? with the ?cell scrambler? block highlighted. figure 32: illustration of the tran smit atm cell processor block fun ctional block diagram with the ?cell scrambler? block highlighted parity checker block parity checker block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte calculation & insertion block hec byte calculation & insertion block cell payload scrambler block cell payload scrambler block txfifo txfifo transmit utopia interface block microprocessor interface block microprocessor interface block idle cell generator idle cell generator main data path to transmit sts-3c/sts-12c poh processor block transmit gfc nibble-field input port block transmit gfc nibble-field input port block txgfc input port if the ?cell payload scrambler? block is enabled, then it will scramble the payload bytes (within each outbound atm cell) per the polynomial x 43 + 1. historically, the purpose of the cell payload scrambler block is to prevent the contents of payload bytes fr om mimicking certain framing alignment bytes, within a given standard transport medium. however, this rationale is not very important in sonet applications, in which all bytes (with the exception of the a1 and a2 bytes) within t he ?outbound? sts-n or sts-nc data-stream are also scrambled. if should be noted that the ?cell payload scrambler? block only scrambles the pay load bytes. the ?cell payload scrambler? block does not alter the value of the five (5) header bytes within each outbound atm cell. the user can enable the ?cell payload scrambler? bl ock by setting bit 1 (cell payload scramble enable), within the ?transmit atm control ? byte 0? register; as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 207 transmit atm control ? byte 0 (address = 0xnf03) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 hec byte invert hec byte check enable parity check enable discard cell upon parity error odd parity unused cell payload scramble enable r/w r/w r/w r/w r/w r/o r/o r/w x x 0 x x 0 0 1 note: this particular setting does not enable nor disable the ce ll de-scrambler within the receive atm cell processor block. the user will need to separately enable or disabl e the cell de-scrambler per the instructions presented in section _. 2.2.6.14 t he t est c ell g enerator b lock the transmit atm cell processor block consists of a te st cell generator block. similarly, the receive atm cell processor block has a corresponding test cell receiver. 2.2.6.15 transmit atm cell processor block interrupts the transmit atm cell processor block is ca pable of generating the following interrupts. ? the ?transmit cell extraction? interrupt ? the ?transmit cell insertion? interrupt ? the ?transmit cell extraction memory overflow? interrupt ? the ?transmit cell inserti on memory overflow? interrupt ? the ?detection of hec byte error? interrupt ? the ?detection of parity error? interrupt this section describes the followi ng aspects of these interrupts. ? the conditions causing these interrupts to be declared ? instructions on how to enable or disable interrupts ? instructions on how to services these interrupts the transmit cell extraction interrupt the transmit atm cell processor block will generate the ?transmit cell extraction? interrupt anytime the ?cell extraction? buffer receives a new ?copied? atm cell from t he user cell filter. the purpose of this interrupt is to notify the microprocessor that t he ?cell extraction? buffer contains an atm cell that needs to be read out via the microprocessor interface.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 208 enabling the transmit cell extraction interrupt the user can enable the ?transmit cell extraction? interrupt by executing the following steps. step 1 ? write the value ?1? into bit 3 (transmit atm cell processor block interrupt enable), within the ?operation block interrupt enable register ? byte 0?, as depicted below. operation block interrupt enable register ? byte 0 (address = 0x0017) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive atm cell processor block interrupt enable receive sts-3 toh block interrupt enable receive sonet/ vc-3 poh block interrupt enable receive ppp processor block interrupt enable transmit atm cell processor block interrupt enable unused transmit ppp processor block interrupt enable r/w r/w r/w r/w r/w r/o r/o r/w 0 0 0 0 1 0 0 0 note: this step enables the ?transmit atm cell processor? bl ock for interrupt generation, at the ?block level?. step 2 ? set bit 5 (cell extraction interrupt enable), within the ?transmit atm cell processor ? interrupt enable register? to ?1? as depicted below. transmit atm cell processor ? interrupt enable register (address = 0xnf0f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt enable cell insertion interrupt enable cell extraction memory overflow interrupt enable cell insertion memory overflow interrupt enable detection of hec byte error interrupt enable detection of parity error interrupt enable r/o r/o r/w r/w r/w r/w r/w r/w 0 0 1 0 0 0 0 0 this step enables the ?transmit cell extraction? interrupt, at the ?source-lev el?. once the user executes this write operation, then the transmit atm cell processor bl ock will generate an interrupt to the microprocessor anytime that the user cell filter copies a cell, and r outes the ?replicate? cell to the ?transmit cell extraction buffer?. servicing the transmit cell extraction interrupt once the xrt94l33 generates an interrupt, then the user must develop the interrupt service routine such that it executes the following steps.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 209 step 1 ? read out the contents of both the operati on block interrupt status register ? byte 1 and byte 0. the bit-format of these two registers is presented below. operation block interrupt status register ? byte 1 (address = 0x0012) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 op control block interrupt status unused r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 operation block interrupt status register ? byte 0 (address = 0x0013) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive atm cell processor block interrupt status receive sts-3 toh block interrupt status receive sonet/vc-3 poh block interrupt status receive ppp processor block interrupt status transmit atm cell processor block interrupt status unused transmit ppp processor block interrupt status r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 1 0 0 0 note: if the transmit atm cell processor block is the source of the interrupt, then bit 3 (t ransmit atm cell processor block interrupt status), within the ?o peration block interrupt status register ? byte 0? will be set to ?1?, as depicted above. step 2 ? after the microprocessor has determined that the transmit atm cell processor block is the ?interrupting? functional block, within the xrt94l33, it must now identify which of the four channels has generated this interrupt. the microprocessor can accomplish this by reading out the contents of the ?operation channel interrupt indicator ? transmit atm cell processor block. the bit-fo rmat of the ?operation channel interrupt indicator ? transmit atm cell processor block? is presented below. operation channel interrupt indicator ? transmit atm cell processor block (address = 0x0122) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused transmit atm cell processor block - channel 3 interrupt indication status transmit atm cell processor block - channel 2 interrupt indication status transmit atm cell processor block - channel 1 interrupt indication status transmit atm cell processor block channel 0 interrupt indication status r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 this register permits the user to identify which of t he four transmit atm cell processor blocks within the xrt94l33 are generating this particular interrupt request.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 210 step 3 ? after the microprocessor has determined which of the four transmit atm cell processor blocks is the ?interrupting? block within the xrt94l 33, then it should read out the contents of the corresponding ?transmit atm cell processor ? interrupt status register?. this will permit the microprocessor to identify the exact cause of the inte rrupt request, from the transmit atm cell processor block. the bit-format of ?transmit atm cell processor ? interr upt status? register is presented below. transmit atm cell processor ? interrupt status register (address = 0xnf0b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt status cell insertion interrupt status cell extraction memory overflow interrupt status cell insertion memory overflow interrupt status detection of hec byte error interrupt status detection of parity error interrupt status r/o r/o rur rur rur rur rur rur 0 0 1 0 0 0 0 0 if the cause of this interrupt is the ?transmit cell extraction ? interrupt, then bit 5 (c ell extraction interrupt status) within the ?transmit atm cell processor ? interrupt st atus register? will be se t to ?1? as depicted above. recommended subsequent action once the microprocessor interface has identified th is particular interrupt as being the ?transmit cell extraction? interrupt, then the user is advised to read out the contents of the ?transmit cell extraction? buffer. the procedure for reading out the co ntents of the ?transmit cell extrac tion? buffer is presented in section 4.2.2.4. the transmit cell insertion interrupt the transmit atm cell processor block will generate t he ?transmit cell insertion? interrupt anytime the ?transmit cell insertion? processor transmits an atm cell into the ?transmit data path? (thereby ?freeing up? space for another atm cell to be written into the ?cell in sertion? buffer). the purpos e of this interrupt is to notify the microprocessor that the ?tra nsmit cell insertion? buffer contains sufficient available space to accept at least one more atm cell from the microprocessor. enabling the ?transmit cell insertion? interrupt the user can enable the ?cell insertion? in terrupt by executing the following steps.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 211 step 1 ? write the value ?1? into bit 3 (transmit atm cell processor block interrupt enable), within the ?operation block interrupt enable? register ? byte 0? as depicted below. operation block interrupt enable register ? byte 0 (address = 0x0017) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive atm cell processor block interrupt enable receive sts-3 toh block interrupt enable receive sonet/ vc-3 poh block interrupt enable receive ppp processor block interrupt enable transmit atm cell processor block interrupt enable unused transmit ppp processor block interrupt enable r/w r/w r/w r/w r/w r/o r/o r/w 0 0 0 0 1 0 0 0 note: this step enables the ?transmit atm cell processor? bl ock for interrupt generation, at the ?block level?. step 2 ? set bit 4 (cell insertion interrupt enable), within the ?transmit atm cell processor ? interrupt enable register? to ?1? as depicted below. transmit atm cell processor ? interrupt enable register (address = 0xnf0f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt enable cell insertion interrupt enable cell extraction memory overflow interrupt enable cell insertion memory overflow interrupt enable detection of hec byte error interrupt enable detection of parity error interrupt enable r/o r/o r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 0 this step enables the ?transmit cell insertion? interrupt at the ?source-level?. once the user executes this write operation, then the transmit atm cell processor bl ock will generate an interrupt to the microprocessor anytime that the ?transmit cell insertion? processor inse rts a cell into the ?transmit data path? and ?frees up? space for a new atm cell to be written into the ?cell insertion? buffer. this interrupt is most useful, when the microprocessor is attempting to load a cell into the ?transmit cell insertion? buffer, but determines that the ?tra nsmit cell insertion? buffer is currently full. servicing the transmit cell insertion interrupt once the xrt94l33 generates an interrupt, then the user must develop the interrupt service routine such that it executes the following steps.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 212 step 1 ? read out the contents of both the operati on block interrupt status register ? byte 1 and byte 0. the bit-format of these two registers is presented below. operation block interrupt status register ? byte 1 (address = 0x0012) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 op control block interrupt status unused r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 operation block interrupt status register ? byte 0 (address = 0x0013) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive atm cell processor block interrupt status receive sts-3 toh block interrupt status receive sonet/vc-3 poh block interrupt status receive ppp processor block interrupt status transmit atm cell processor block interrupt status unused transmit ppp processor block interrupt status r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 1 0 0 0 note: if the transmit atm cell processor block is the source of the interrupt, then bit 3 (t ransmit atm cell processor block interrupt status), within the ?o peration block interrupt status register ? byte 0? will be set to ?1?, as depicted above. step 2 ? after the microprocessor has determined that the transmit atm cell processor block is the ?interrupting? functional block, within the xrt94l33, it must now identify which of the four channels has generated this interrupt. the microprocessor can accomplish this by reading out the contents of the ?operation channel interrupt indicator ? transmit atm cell processor block. the bit-fo rmat of the ?operation channel interrupt indicator ? transmit atm cell processor block? is presented below. operation channel interrupt indicator ? transmit atm cell processor block (address = 0x0122) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused transmit atm cell processor block - channel 3 interrupt indication status transmit atm cell processor block - channel 2 interrupt indication status transmit atm cell processor block - channel 1 interrupt indication status transmit atm cell processor block channel 0 interrupt indication status r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 this register permits the user to identify which of t he four transmit atm cell processor blocks within the xrt94l33 are generating this particular interrupt request.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 213 step 3 ? after the microprocessor has determined which of the four transmit atm cell processor blocks is the ?interrupting? block within the xrt94l 33, then it should read out the contents of the corresponding ?transmit atm cell processor ? interrupt status register?. this will permit the microprocessor to identify the exact cause of the inte rrupt request, from the transmit atm cell processor block. the bit-format of ?transmit atm cell processor ? interr upt status? register is presented below. transmit atm cell processor ? interrupt status register (address = 0xnf0b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt status cell insertion interrupt status cell extraction memory overflow interrupt status cell insertion memory overflow interrupt status detection of hec byte error interrupt status detection of parity error interrupt status r/o r/o rur rur rur rur rur rur 0 0 0 1 0 0 0 0 if the cause of this interrupt is the ?transmit cell insert ion? interrupt, then bit 4 (cell insertion interrupt status) within the ?transmit atm cell processor ? interrupt st atus register? will be set to ?1? as depicted above. recommended subsequent action once the microprocessor interface has identified this par ticular interrupt as being the ?transmit cell insertion? interrupt, then this means that some space within the tr ansmit cell insertion buffer has been ?freed-up?. as a consequence, the user can respond to this interrupt by writing in another atm cell into the transmit cell insertion buffer. the procedure for writing the contents of an atm cell into the ?transmit cell insertion? buffer is presented in section 4.2.2.3. the transmit cell extraction memory overflow interrupt the transmit atm cell processor block will generate the ?transmit cell extraction memory overflow? interrupt anytime the transmit cell extraction buffer is currently full, and the transmit cell extraction processor reads in another ?copied? atm cell into the ?tra nsmit cell extraction? buffer. in this case, some of the data residing within the ?transmit cell extr action? buffer will be over written and will be lost. note: if the ?transmit atm cell processor? block generates the ?transmit cell extraction? memory overflow interrupt this is typically the result of the microprocessor not reading out the contents of the transmit cell extraction memory quickly or often enough before another atm cell is ?copied? by the transmit user cell? filter. additionally, this particular interrupt should serve as a wa rning that the ?transmit cell extraction? buffer likely contains some erred data. enabling the ?transmit cell extraction memory overflow? interrupt the user can enable the ?transmit cell extraction me mory overflow? interrupt by executing the following steps.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 214 step 1 ? write the value ?1? into bit 3 (transmit atm cell processor block interrupt enable), within the ?operation block interrupt enable? register ? byte 0? as depicted below. operation block interrupt enable register ? byte 0 (address = 0x0017) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive atm cell processor block interrupt enable receive sts-3 toh block interrupt enable receive sonet/ vc-3 poh block interrupt enable receive ppp processor block interrupt enable transmit atm cell processor block interrupt enable unused transmit ppp processor block interrupt enable r/w r/w r/w r/w r/w r/o r/o r/w 0 0 0 0 1 0 0 0 note: this step enables the ?transmit atm cell processor? bl ock for interrupt generation, at the ?block level?. step 2 ? set bit 3 (cell extraction memory overflow interrupt enable), within the ?transmit atm cell processor ? interrupt enable register? to ?1? as depicted below. transmit atm cell processor ? interrupt enable register (address = 0xnf0f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt enable cell insertion interrupt enable cell extraction memory overflow interrupt enable cell insertion memory overflow interrupt enable detection of hec byte error interrupt enable detection of parity error interrupt enable r/o r/o r/w r/w r/w r/w r/w r/w 0 0 0 0 1 0 0 0 this step enables the ?transmit cell extraction memory overflow? interrupt at the ?source-level?. once the user executes this write operation, then the transmit atm cell processo r block will generate an interrupt to the microprocessor anytime the ?tra nsmit cell extraction buffer? experie nces an ?overflow? condition.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 215 2.2.7 transmit sts-3 c poh processor block ( for atm/ppp over sts-3 c a pplications ) all outbound atm cells that exit the transmit atm cell processor block will be routed to the transmit sts-3c poh processor block, where they will be mapped into either sts- 3c spes. likewise, all outbound ppp packets that exit the transmit ppp packet processor block will be rout ed to the transmit sts-3c poh processor block, wher e they will be mapped into sts-3c spes. t he purpose of the transmit sts-3c poh processor block is to accomplish the following. ? to accept atm cells from the transmit atm cell processor block and to map these cells into sts-3c spe (synchronous payloa d envelope), or ? to accept ppp packets from the transmit ppp packet processor block and to map these packets into sts-3c spes ? to compute and insert the b3 (path bip-8) byte ? to deliberately transmit an sts-3c spe with an erred b3 byte (for testing purposes) ? to source the j1, c2, g1, f2, h4, z3, z4 and z5 bytes. ? to automatically transmit the rdi-p (path ? remote defect) indicator whenever (and for the duration that) the corresponding receive sts-3c poh processor block declares the ais-p, lop-p, uneq-p, tim-p or plm-p defect conditions. ? to automatically transmit the rdi-p indicator wh enever (and for the duration that) the corresponding receive atm cell processor block declares the lcd defect condition. ? to transmit the rdi-p indicator upon software control. ? to automatically transmit the rei-p (path ? remote error) indicator anytime the corresponding receive sts-3c poh processor block detects b3 byte e rrors in its incoming sts-3c spe data-stream. ? to transmit the rei-p indicator upon software control. ? to transmit the ais-p (path ? alarm indica tion signal) indicator upon software control. ? to permit the user to transmit either 1 byte, 16 byte or 64 byte path trace messages to the remote pte. ? to force ?positive-stuff? pointer adjustm ents in the outbound sts-3c data-stream. ? to force ?negative-stuff? pointer adjus tments in the outbound sts-3c data-stream. ? to force single and continuous ndf (new data flag) events into the outbound sts-3c data-stream ? to route its output data to the transmit sts- 3c toh processor block for further processing. figure 33 presents an illustration of the block diagram of the xrt94l33 mapper ic, with the ?transmit sts- 3c poh processor? block highlighted.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 216 figure 33: illustration of the functi onal block diagram of the xrt94l 33 mapper ic, with the transmit sts-3c poh processor block high-lighted transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3 toh processor block receive sts-3 toh processor block transmit sts-3 toh processor block transmit sts-3 toh processor block receive sts-3c poh processor block receive sts-3c poh processor block transmit sts-3c poh processor block transmit sts-3c poh processor block sts-3 telecom bus interface block sts-3 telecom bus interface block sts-3 pecl interface block sts-3 pecl interface block sts-3 cdr block sts-3 cdr block xrt94l33 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block some background information on the path overhead (poh) bytes for sts-3c applications, the size of the spe is 9 rows by 261 byte columns. figure 34 presents a simple illustration of the sts-3c spe. figure 34 simple illustration of the sts-3c spe in each case, the first byte column within an sts- 3c spe is referred to as the path overhead (poh). therefore, in all, the poh consists of a total of nine (9) bytes. each of these poh bytes is briefly described below. j1 ? the path trace byte b3 ? the path bip-8 byte c2 ? the payload label byte g1 ? the path status byte f2 ? the path user channel byte h4 ? the multi-frame indicator (not used for atm and ppp applications) z3, z4 and z5 ? growth bytes the remainder of this section describes how the transmit sts-3c poh processor block handles these poh bytes. the operation of the ?transmit sts-3c poh processor? block is discussed in some detail below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 217 2.2.7.1 receiving atm cell data from the transmit atm cell processor block the transmit sts-3c poh processor block receives atm cell data from the transmit atm cell processor block; and maps this data into an sts-3c spe. as the transmit sts-3c poh processor block receives this atm cell data from the transmit atm cell processor block, it will perfo rm the following functions. ? it will map these atm cells into the pay load bytes, within the sts-3c spe. ? compute and insert the b3 byte ? source (per user configuration) the j1, c2, g1, f2, h4, z3, z4 and z5 bytes ? to (automatically or upon softwar e command) transmit the rdi-p (path ? remote defect indicator) indicator ? to (automatically or upon software command) tran smit the rei-p (path ? remote error indicator) indicator ? to (upon software command) transmit the ais-p (path ? alarm indication signal) indicator ? to (upon software command) force pointer-adjustment or ndf (new data flag) events into the outbound sts-3c data-stream. each of these functions is described in detail below. 2.2.7.2 computation and insertion of the path bip-8 (b3) byte the transmit sts-3c poh processor block creates sts- 3c spe data and computes a bip-8 value over this sts-3c spe. the results of this calc ulation are inserted into the b3 byte-p osition within the very next sts-3c spe. the remote pte (path terminating equipment) will use this byte, in order to perform error- checking/detection on the incoming sts-3c spe data that it receives. transmission of erred b3 bytes in the outbound st s-3c data-stream the transmit sts-3c poh processor block permits the user to insert errors into the ?b3 bytes?, within the outbound sts-3c spe data-stream. the user can accomplish this by writing a non-zero va lue into the ?transmit sts-3c path ? transmitter b3 byte error mask? register. the ?transmit sts-3c po h processor block will perf orm an xor operation with the contents of the ?outbound? b3 byte, and the contents of this register. the results of this calculation are written back into the b3 byte position, within the outbound sts-3c spe data-stream. the bit-format of the ?transmit sts-3c path ? transm it b3 byte error mask? re gister is presented below. transmit sts-3c path ? transmitter b3 byte error mask register (address = 0x1997) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_b3_byte_mask[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 note: for normal (e.g., un-erred) operation, the user should ensure that this register is set to ?0x00? (the default value).
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 218 2.2.7.3 transmission of path-alarm conditions the transmit sts-3c poh processor bl ock supports the following functions. ? transmitting the ais-p pattern (under software control) ? transmitting the rdi-p indicator ( automatically and under software control) ? transmitting the rei-p indicator ( automatically and under software control) each of these operations is discussed in detail below. 2.2.7.3.1 transmission of the ais-p pattern the transmit sts-3c poh processor block can be conf igured to generate and transmit the ais-p (path ais) indicator to the remote pte, under software control. the user can accomplish this by setting bit 0 (trans mit ais-p enable) within the ?transmit sts-3c path ? sonet control register ? byte 0? to ?1?, as depicted below. transmit sts-3c path ? sonet control register ? byte 0 (address = 0x1983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 0 0 0 0 0 0 0 1 once the user executes this step, then the ?trans mit sts-3c poh processor? block will do the following. ? it will set all bytes, within the sts-3c spe to an ?all ones? pattern. ? it will set the h1, h2 and h3 bytes (w ithin the toh) to an ?all ones? pattern. please note that whenever the user configures the transmit sts-3c poh processor block to transmit the ais-p indicator, then no atm cells or ppp packe ts will be transmitted to the remote terminal. 2.2.7.3.2 transmission of the rdi-p indicator the transmit sts-3c poh processor block can be c onfigured to transmit the rdi-p indicator either automatically, upon software control or via the ?txp oh_n? external input port as described below. 2.2.7.3.2.1 configuring the transm it sts-3c poh processor block to automatically transmit the rdi-p indicator the user can configure the transmit sts-3c poh pr ocessor block to automatic ally transmit the rdi-p indicator whenever the corresponding receive sts-3c poh processor block declares a plm-p (path ? payload label mismatch), uneq-p (path ? unequipped), lop-p (path ? loss of pointer), ais-p, tim-p (path - trace identificat ion mismatch), and lcd-p (path ? loss of cell delineation) condition. the procedure for configuring the transmit sts-3c poh processor block to automatic ally transmit the rdi-p indicator, for each of the above-ment ioned defects is presented below. 2.2.7.3.2.2 configuring the tran smit sts-3c poh processor block to automatically transmit rdi- p, in response to declaration of the plm-p condition the user can configure the transmit sts-3c poh pr ocessor block to automatic ally transmit the rdi-p indicator, in response to the corresponding receiv e sts-3c poh processor block declaring the plm-p condition, by executing the following steps.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 219 step 1 ? write the value [0, 0] into bits 3 and 4 (rdi-p insertion type[1, 0]) within the ?transmit sts- 3c path ? sonet control register ? byte 0? as depicted below. transmit sts-3c path ? sonet control register ? byte 0 (address = 0x1983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 this step configures the ?transmit sts-3c poh processor? block to automatically set bits 5 through 7 (of the g1 byte) within the outbound sts-3c spe; to the appropriate ?rdi-p val ue? based upon receiv e conditions as detected by the corresponding ?receive sts-3c poh processor? block. step 2 ? write the appropriate value into bits 3 through 1 (plm-p rdi-p code[2:0]) within the ?transmit sts-3c path ? rdi-p control re gister ? byte 2? as illustrated below. transmit sts-3c path ? rdi-p control register ? byte 2 (address = 0x19c9) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lcd-p rdi-p code[2:0] transmit rdi-p upon lcd-p plm-p rdi-p code[2:0] transmit rdi-p upon plm-p r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 x x x 0 by writing this particular value into these three bit-fiel ds, the user is specifying the value that the ?transmit sts-3c poh processor? block will se t the rdi-p bit-fields (within the ?outbound g1 byte) to, whenever the corresponding receive sts-3c poh processor block declares the plm-p condition. step 3 ? set bit 0 (transmit rdi-p upon plm-p) with in the ?transmit sts-3c path ? rdi-p control register ? byte 2? to ?1?, as illustrated below. transmit sts-3c path ? rdi-p contro l register ? byte 2 (address = 0x19c9) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lcd-p rdi-p code[2:0] transmit rdi-p upon lcd-p plm-p rdi-p code[2:0] transmit rdi-p upon plm-p r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 x x x 1 this step configures the transmit sts-3c poh processo r block to automatically transmit the rdi-p indicator (per the values written into bits 3 through 1; within this register), anytime the corresponding receive sts-3c poh processor block detects the ?plm-p? condition.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 220 2.2.7.3.2.3 configuring the tran smit sts-3c poh processor block to automatically transmit rdi- p, in response to declaration of the uneq-p condition the user can configure the transmit sts-3c poh pr ocessor block to automatic ally transmit the rdi-p indicator, in response to the corresponding receiv e sts-3c poh processor block declaring the uneq-p condition, by executing the following steps. step 1 ? write the appropriate value into bits 3 through 1 (uneq-p rdi-p code[2:0]) within the ?transmit sts-3c path ? rdi-p condition register ? byte 1, as illustrated below. transmit sts-3c path ? rdi-p control register ? byte 1 (address = 0x19ca) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 tim-p rdi-p code[2:0] transmit rdi-p upon tim-p uneq-p rdi-p code[2:0] transmit rdi-p upon uneq-p r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 x x x 0 by writing this particular value into these bit-fields th e user is specifying the value that the ?transmit sts-3c poh processor? block will set the rdi-p bit-fields (withi n the g1 byte of outbound sts-3c frame) to whenever the corresponding receive sts-3c poh proces sor block declares the uneq-p condition. step 2 ? set bit 0 (transmit rdi-p upon uneq-p) within the ?transmit sts-3c path ? rdi-p control register ? byte 1? to ?1?, as illustrated below. transmit sts-3c path ? rdi-p control register ? byte 1 (address = 0x19ca) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 tim-p rdi-p code[2:0] transmit rdi-p upon tim-p uneq-p rdi-p code[2:0] transmit rdi-p upon uneq-p r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 x x x 1 this step configures the transmit sts-3c poh proces sor block to transmit the rdi-p indicator (per the values written into bits 3 through 1, within this r egister); anytime the corresponding ?receive sts-3c poh processor? block declares the ?uneq-p? condition.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 221 2.2.7.3.2.4 configuring the tran smit sts-3c poh processor block to automatically transmit rdi- p, in response to declaration of the lop-p condition the user can configure the transmit sts-3c poh pr ocessor block to automatic ally transmit the rdi-p indicator, in response to the corresponding receive sts-3c poh processor block declaring the lop-p condition, by executing the following steps. step 1 ? write the appropriate value into bits 7 through 5 (lop-p rdi-p code[2:0]) within the ?transmit sts-3c path ? rdi-p control re gister ? byte 0?; as illustrated below. transmit sts-3c path ? rdi-p control register ? byte 0 (address = 0x19cb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lop-p rdi-p code[2:0] transmit rdi-p upon lop-p ais-p rdi-p code[2:0] transmit rdi-p upon ais-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 0 0 0 0 0 by writing this particular value into these three bit-fi elds, the user is specifying the value that the transmit sts-3c poh processor block will set th e rdi-p bit-fields (in the g1 byte, within the ?outb ound? sts-3c data- stream) whenever the corresponding receive sts-3c poh processor block declares the lop-p condition. step 2 ? set bit 4 (transmit rdi-p upon lop-p) within the ?transmit sts-3c path ? rdi-p control register ? byte 0? to ?1?; as illustrated below. transmit sts-3c path ? rdi-p control register ? byte 0 (address = 0x19cb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lop-p rdi-p code[2:0] transmit rdi-p upon lop-p ais-p rdi-p code[2:0] transmit rdi-p upon ais-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 1 0 0 0 0 this step configures the transmit sts-3c poh processo r block to automatically transmit the rdi-p indicator (per the values written into bits 3 through 1, within th is register); anytime the co rresponding ?receive sts-3c poh processor? block declares the ?lop-p? condition. 2.2.7.3.2.5 configuring the tran smit sts-3c poh processor block to automatically transmit rdi- p, in response to declaration of the ais-p condition the user can configure the transmit sts-3c poh pr ocessor block to automatic ally transmit the rdi-p indicator, in response to the corresponding receive st s-3c poh processor declaring the ais-p condition, by executing the following steps.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 222 step 1 ? write the appropriate value into bits 3 through 1 (ais-p rdi-p code[2:0]) within the ?transmit sts-3c path ? rdi-p control re gister ? byte 0?; as illustrated below. transmit sts-3c path ? rdi-p control register ? byte 0 (address = 0x19cb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lop-p rdi-p code[2:0] transmit rdi-p upon lop-p ais-p rdi-p code[2:0] transmit rdi-p upon ais-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 1 x x x 0 by writing this particular value into these three bit-fi elds, the user is specifying the value that the transmit sts-3c poh processor block will set th e rdi-p bit-fields (in the g1 byte, within the ?outb ound? sts-3c data- stream) whenever the corresponding receive sts-3c poh processor block declares the ais-p condition. step 2 ? set bit 0 (transmit rdi-p upon ais-p) within the ?transmit sts-3c path ? rdi-p control register ? byte 0?, as illustrated below. transmit sts-3c path ? rdi-p control register ? byte 0 (address = 0x19cb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lop-p rdi-p code[2:0] transmit rdi-p upon lop-p ais-p rdi-p code[2:0] transmit rdi-p upon ais-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 1 x x x 1 this step configures the transmit sts-3c poh processo r block to automatically transmit the rdi-p indicator (per the values written into bits 3 through 1, within th is register); anytime the co rresponding ?receive sts-3c poh processor? block declares the ?ais-p? condition. 2.2.7.3.2.6 configuring the tran smit sts-3c poh processor block to automatically transmit rdi- p, in response to declaration of the tim-p condition the user can configure the transmit sts-3c poh pr ocessor block to automatic ally transmit the rdi-p indicator, in response to the corresponding receiv e sts-3c poh processor block declaring the tim-p condition, by executing the following steps. step 1 ? write the appropriate value into bits 7 through 5 (tim-p rdi-p code[2:0]) within the ?transmit sts-3c path ? rdi-p condition register ? byte 1; as illustrated below. transmit sts-3c path ? rdi-p control register ? byte 1 (address = 0x19ca) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 tim-p rdi-p code[2:0] transmit rdi-p upon tim-p uneq-p rdi-p code[2:0] transmit rdi-p upon uneq-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 0 x x x x
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 223 by writing this particular value into these bit-fields th e user is specifying the value that the ?transmit sts-3c poh processor? block will set the rdi-p bit-fields (w ithin the g1 byte of the outbound sts-3c frame) to whenever the corresponding receive sts-3c poh processor block declares the tim-p condition. step 2 ? set bit 4 (transmit rdi-p upon tim-p) within the ?transmit sts-3c path ? rdi-p control register ? byte 1?; to ?1? as illustrated below. transmit sts-3c path ? rdi-p control register ? byte 1 (address = 0x19ca) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 tim-p rdi-p code[2:0] transmit rdi-p upon tim-p uneq-p rdi-p code[2:0] transmit rdi-p upon uneq-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 1 x x x x this step configures the transmit sts-3c poh proces sor block to transmit the rdi-p indicator (per the values written into bits 3 through 1, within this r egister); anytime the corresponding ?receive sts-3c poh processor? block declares the ?tim-p? condition. 2.2.7.3.2.7 configuring the tran smit sts-3c poh processor block to automatically transmit rdi- p, in response to declaration of the lcd-p condition the user can configure the transmit sts-3c poh pr ocessor block to automatic ally transmit the rdi-p indicator, in response to the corresponding receiv e sts-3c poh processor block declaring the lcd-p condition, by executing the following steps. step 1- write the appropriate value into bit 7 through 5 (lcd-p rdi-p code[2:0]) within the ?transmit sts-3c path ? rdi-p control register ? byte 2? as illustrated below. transmit sts-3c path ? rdi-p control register ? byte 2 (address = 0x19c9) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lcd-p rdi-p code[2:0] transmit rdi-p upon lcd-p plm-p rdi-p code[2:0] transmit rdi-p upon plm-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 0 x x x 0 by writing this particular value into these three bit-fiel ds, the user is specifying the values that the ?transmit sts-3c poh processor? block will set the rdi-p bit-fields (within the out bound g1 byte) to, whenever the corresponding receive sts-3c poh proces sor block declares the lcd-p condition.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 224 step 2 ? set bit 4 (transmit rdi-p upon lcd-p) within the ?transmit sts-3c path ? rdi-p control registers ? byte 2? to ?1?, as illustrated below. transmit sts-3c path ? rdi-p control register ? byte 2 (address = 0x19c9) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lcd-p rdi-p code[2:0] transmit rdi-p upon lcd-p plm-p rdi-p code[2:0] transmit rdi-p upon plm-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 1 x x x 0 2.2.7.3.2.8 configuring the transmit sts-3c poh pr ocessor block to transmit the rdi-p indicator, upon software control the user can configure the transmit sts-3c poh pr ocessor block to transmit the rdi-p (per software command) by executing the following steps. step 1 ? write the value ?[0, 1]? into bits 3 and 4 (rdi-p insertion type[1:0]) within the ?transmit sts-3c path ? sonet control register ? byte 0?, as depicted below. transmit sts-3c path ? sonet control register ? byte 0 (address = 0x1983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 0 0 0 0 1 0 0 0 this step configures the ?transmit sts-3c poh proces sor? block to automatically read out the contents of bits 3 through 1 (of the ?transmit sts-3c path ? g1 byte value? register); and writ e the value of these bits into bits 5 through 7 (of the g1 byte) within the ?outb ound? sts-3c spe. the bit-fo rmat of the ?transmit sts- 3c path ? g1 byte value? register (with t he appropriate bits ?shaded?) is presented below. transmit sts-3c path ? transmit g1 byte value register (address = 0x199f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_g1_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 x x x 0 in this mode, the user can transmit an ?un-erred? in dicator by setting bits 3 through 1 (within the transmit sts-3c path ? transmit g1 byte value? register) to [0, 0, 0]. conversely, t he user can now transmit an ?erred? indicator by setting bits 3 through 1 (within t he ?transmit sts-3c path ? transmit g1 byte value? register) to some value other than [0, 0, 0].
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 225 2.2.7.3.2.9 configuring the transmit sts-3c poh pr ocessor block to transmit the rdi-p indicator, via the ?txpoh_n? input port. the user can configure the transmit sts-3c poh proces sor block to transmit the rdi-p (per external input port) by executing the following steps. step 1 ? write the value ?[1, 0]? into bits 3 and 4 (rdi-p insertion type[1:0]) within the ?transmit sts-3c path ? sonet control register ? byte 0?, as depicted below. transmit sts-3c path ? sonet control register ? byte 0 (address = 0x1983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 0 0 0 1 0 0 0 0 this step configures the ?transmit st s-3c poh processor? block to set the value of the rdi-p bit-fields (within the outbound sts-3c spe) based up on the data that it receives via th e ?txpoh_n? input port. in this mode, the transmit sts-3c poh processor block will acc ept the value, corresponding to the rdi-p bit-fields (via the ?txpoh_n input port?) and it will write this data into the ?outbound? sts-3c spe data-stream. step 2 ? begin providing the values of the ?outbound? rdi-p bit-fields to the ?txpoh_n? input port. the procedure for applying the rdi-p bit-values to the ?txpoh_n? input port is presented below. using the ?txpoh? input port to insert the rd i-p bit values into the outbound sts-3c spe data- stream if the user intends to externally in sert the rdi-p bits into the outbound sts-3c spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 35.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 226 figure 35: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (infigure 35) is ?dashed? because cont rolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., where it waits for 25 periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit this ?wait state? and then place the very first bit of the ?outbound? rdi-p bit-fields onto the ?txpoh_n? input pi n, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the g1 by te is the 4th byte within the poh; and bit 7 (which is the very first rdi-p bit to be latched into the external input interface is the second bit within the g1 byte to be processed). ? afterwards, the ?external circuit? should serially pl ace the remaining two bits (of the rdi-p bits) onto the ?txpoh_n? input pin, upon each of the next two falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 227 2.2.7.3.3 transmission of the rei-p indicator the transmit sts-3c poh processor block can be conf igured to transmit the rei-p indicator either (1) automatically, (2) upon software command or (3) via the ?txpoh_n? input port as described below. 2.2.7.3.3.1 configuring the transm it sts-3c poh processor block to automatically transmit the rei-p indicator the user can configure the transmit sts-3c poh pr ocessor block to automatic ally transmit the rei-p indicator whenever the corresponding receive sts-3c poh processor block detects at least one b3 byte error within its incoming sts-3c spe data-stream. the user can configure the transmit sts-3c poh pr ocessor block to automatic ally transmit the rei-p indicator, in response to detection of b3 by te errors, by executing the following steps. step 1 ? write the value [0, 0] into bits 5 and 6 (rei-p insertion type[1, 0]) within the ?transmit sts- 3c path ? sonet control register ? byte 0? as depicted below. transmit sts-3c path ? sonet control register ? byte 0 (address = 0x1983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type c2 byte auto insert mode enable transmit ais-p enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 this step configures the ?transmit sts-3c poh processor? block to automatically set bits 1 through 4 (of the g1 byte) within the ?outbound? sts-3c spe to the ap propriate rei-p value, based upon receive conditions as detected by the corresponding receiv e sts-3c poh processor block. step 2 ? indicate whether the rei-p value (transmitted to the remote pte) reflects the number of bits (within the b3 byte) that are in error, or the number of erred sts-3c spe that have been detected by the corresponding receive sts-3c poh processor block. the xrt94l33 permits the user to (1) flag b3 byte erro rs, and (2) to transmit the resulting rei-p value (back out to the remote pte) by the following means. ? by flagging and reporting the number of bits (within the b3 byte) that have be determined to be in error, within a given sts-3c spe. ? by flagging and reporting whether or not the corr esponding receive sts-3c poh processor block is currently receiving erred sts-3c spe. the user can choose between these two options by writ ing the appropriate value into bit 0 (b3 error type) within the receive sts-3c path ? control register ? byte 0?; as illustrated below. receive sts-3c path ? control register ? byte 0 (address = 0x1183) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused check stuff rdi-p type rei-p error type b3 error type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 x
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 228 setting this bit-field to ?0? configures the transmit st s-3c poh processor block to set the rei-p bit-fields (within the g1 byte of the ?outbound ? sts-3c spe); to a value the reflects the number of bits (within the b3 byte) that were determined to be in error (withi n the most recently rece ived sts-3c spe) by the corresponding receive sts-3c poh processor block. in this case, the rei-p bit-fields can range in value from ?0? (for no b3 bit errors) to ?8 ? (for all b3 bits being in error). setting this bit-field to ?1? configures the transmit st s-3c poh processor block to set the rei-p bit-fields (within the g1 byte of the ?outbound?sts-3c spe); to a value that indicates whethe r or not at least one b3 byte error was detected with in the most recent ly received sts-3c spe; by t he corresponding re ceive sts-3c poh processor block. in this mode, the transmit sts- 3c poh processor block will set the ?rei-p? bit-fields (within the outbound sts-3c spe) to ?0? if the corresponding ?receive st s-3c poh processor? block is not detecting any b3 byte errors, in its incoming sts-3c data-stream. conversely, the transmit sts-3c poh processor block will set the ?rei-p? bi t-fields (within the ?outbound? sts-3c spe) to ?1? if the corre sponding receive sts-3c poh processor block receives an sts-3c spe that contains a b3 byte error. 2.2.7.3.3.2 configuring the transm it sts-3c poh processor block to transmit the rei-p indicator, upon software control the user can configure the transmit sts-3c poh proc essor block to transmit the rei-p indicator (per software command) by executing the following steps. step 1- write the value ?[0, 1]? into bits 5 and 6 (rei-p insertion type[1:0]) within the ?transmit sts- 3c path sonet control register ? byte 0?; as depicted below. transmit sts-3c path ? sonet control register ? byte 0 (address = 0x1983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type c2 byte auto insert mode enable transmit ais-p enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 1 0 0 0 0 0 this step configures the ?transmit sts-3c poh proces sor? block to automatically read out the contents of bits 4 through 7 (of the transmit sts-3c path ? g1 byte value? register) and write the value of these bits into bits 1 through 4 (of the g1 byte) with in the ?outbound? sts-3c spe. the bit-format of the ?transmit sts-3c path ? g1 byte value? register (with the appropriate bits ?shaded?) is presented below. transmit sts-3c path ? transmit g1 byte value register (address = 0x199f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_g1_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 x x x 0 in this mode, the user can transmit an ?un-erred? rei-p value by setting bits 4 through 7 (within the transmit sts-3c path ? transmit g1 byte value? register) to [0, 0, 0, 0]. conversely, the user can transmit an ?erred? rei-p value by setting bits 4 through 7 (within the trans mit sts-3c path ? transmit g1 byte value? register) to some value between 1 and 8.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 229 2.2.7.3.3.3 configuring the transm it sts-3c poh processor block to transmit the rei-p indicator, via the ?txpoh_n? input port the user can configure the transmit sts-3c poh proc essor block to transmit the rei-p (per the external input port) by executing the following steps. step 1 ? write the value [1, 0] into bits 3 and 4 (rei-p insertion type[1:0]) within the ?transmit sts- 3c path ? sonet control register ? byte 0? as depicted below. transmit sts-3c path ? sonet control register ? byte 0 (address = 0x1983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type c2 byte auto insert mode enable transmit ais-p enable r/w r/w r/w r/w r/w r/w r/w r/w 0 1 0 0 0 0 0 0 this step configures the transmit sts-3c poh processor block to set the value of the rei-p bit-fields (within the outbound sts-3c spe) base d upon the data that it receives via t he ?txpoh_n? input por t. in this mode, the transmit sts-3c poh processor block will accept t he value corresponding to the rei-p fields (via the ?txpoh_n input port?) and it will write this dat a into the ?outbound? sts-3c spe data-stream. step 2 ? begin providing the values of the ?outbound? rei-p bit-fields to the ?txpoh_n? input port. the procedure for applying the rei-p bit-values to the ?txpoh_n? input port is presented below. using the ?txpoh? input port to insert the re i-p bit values into th e outbound sts-3c spe data- stream if the user intends to externally in sert the rei-p bits into the outbound sts-3c spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do the following. ? continuously sample the ?txpohenable_n? and the ?txpohenable_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. ? whenever the ?external circuit? samples both t he ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., where it waits for 28 periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit this ?wait state? and then place the very first bit of the ?outbound? rei-p bit-fields onto the ?txpoh _n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and la tched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n? 2.2.7.3.4 transmission of path trace messages via the j1 byte the transmit sts-3c poh processor block permits the us er to transmit path trace messages to the remote pte via the j1 byte. the transmit sts-3c poh proces sor block permits the user to accomplish this by either of the following options. ? automatically set the j1 byte (withi n each outbound sts- 3c spe) to ?0x00? ? set and control the outbound j1 byte via on-chip register ? set and control the outbound j1 byte via external input pin ? use the ?transmit path trace message? buffer
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 230 the details and instructions for using eit her of these features are presented below. 2.2.7.3.4.1 automatically setting the j1 byte (within each outbound sts-3c spe) to ?0x00? the xrt94l33 permits the user to configure each of t he four (4) transmit sts-3c poh processor blocks to automatically set the contents of the j1 byte (w ithin each outbound sts- 3c spe) to ?0x00?. the user can accomplish this by writing the value ?[ 0, 0]? into bits 1 and 0 (j1 type[1:0]) within the appropriate ?transmit sts-3c path ? transmit j1 control? register; as depicted below. transmit sts-3c path ? transmit j1 control? register (address = 0x19bb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j1 message length[1:0] j1 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x 0 0 once the user executes this step, then the correspond ing transmit sts-3c poh processor block(s) will be configured to automatically set the j1 byte (wit hin each outbound sts-3c spe) to the value ?0x00?. 2.2.7.3.4.2 using the ?transmit path trace message? buffer the xrt94l33 contains a total of four (4) ?transmi t path trace message buffers (one for each ?transmit sts-3c poh processor block, within the device). the address location of the ?transmit path trace messag e? buffer, for each of the four transmit sts-3c poh processor blocks is presented below. table 14: address locations of the transmit path trace message buffers within the xrt94l33 t ransmit sts-3 c poh p rocessor b lock - c hannel a ddress l ocation of the t ransmit p ath t race m essage b uffer 0 0x1d00 ? 0x1d3f 1 0x2d00 ? 0x2d3f 2 0x3d00 ? 0x3d3f 3 0x4d00 ? 0x4d3f if the user wishes to use the ?path trace message? buffe r as the means to load and transmit the ?path trace message? to the remote pte, the following steps must be executed. step 1 ? write the contents of this outbound ?path trace message? into the ?transmit path trace message? buffer. as the user writes the contents of the ?outbound? pa th trace message? into the ?transmit path trace? message buffer they must make sure that the first by te of the message is written into address location 0xnc00 (e.g., the very first address location of the ?transmit path trace message? buffer).
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 231 step 2 ? specify the length of this ?path trace message? by writing the appropriate value into bits 3 and 2 (j1 message length[1:0]) within the ?transmit sts-3c path ? transmit j1 control? register; as depicted below. transmit sts-3c path ? transmit j1 control? register (address = 0x19bb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j1 message length[1:0] j1 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x x x the relationship between the contents of ?j1_mess age_length[1:0]? and the corresponding length of the ?path trace message? is presented below in table _. table _, the relationship between the contents of ?j1_message_length[1:0]? and the corresponding ?path trace message? length j1_m essage _l ength [1:0] p ath t race m essage l ength ( bytes ) 00 1 01 16 10 64 11 64 step 3 ? write the value ?[0, 1]? into bits 1 and 0 (j1_type[1:0]) within the transmit sts-3c path ? transmit j1 control register; as depicted below. transmit sts-3c path ? transmit j1 control? register (address = 0x19bb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j1 message length[1:0] j1 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x 0 1 this step configures the transmit sts-3c poh proces sor block to use the contents of the ?transmit path trace message? buffer as the source of the j1 byte, within each ?outbound? sts-3c spe. 2.2.7.3.4.3 setting and controlling the ?out bound? j1 byte via on-chip register the transmit sts-3c poh processor block permits the user to specify the contents of the j1 byte within the ?outbound? sts-3c spe, via software command. the user can configure the transmit sts-3c poh processor block to support this feat ure by performing the following steps. step 1 ? write the value ?[1, 0]? into bits 1 and 0 (j1 type[1:0]) within the ?transmit sts-3c path ? transmit j1 control? register, as depicted below. transmit sts-3c path ? transmit j1 control? register (address = 0x19bb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j1 message length[1:0] j1 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x 1 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 232 this step configures the ?transmit sts-3c poh proces sor? block to read out the contents of the ?transmit path ? transmit j1 byte value? register; and load this value into the ?j1 byte-field? within each outbound sts- 3c spe. step 2 ? write the desired byte value (for the ?outbound? j1 byte) into the ?transmit sts-3c path ? transmit j1 byte value? register. the bit-format of this register is presented below. transmit sts-3c path ? transmitter j1 value register (address = 0x1993) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_j1_byte[7:0] r/w r/w r/w r/w r/w r/w r/w r/w x x x x x x x x 2.2.7.3.4.4 setting and controlling the ?out bound? j1 byte via external input pin the transmit sts-3c poh processor bl ock permits the user to source the contents of the j1 byte via the ?txpoh_n? input port. the user can configure the tr ansmit sts-3c poh processor block to support this feature by performing the following steps. step 1 ? write the value ?[1, 1]? into bits 1 and 0 (j1 type[1:0]) within the ?transmit sts-3c path ? transmit j1 control? register; as depicted below. transmit sts-3c path ? transmit j1 control? register (address = 0x19bb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j1 message length[1:0] j1 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 1 1 this step configures the ?transmit sts-3c poh processor? block to accept the value of the j1 byte, via the ?txpoh_n? input port and load this value into the j1 byte position within each outbound sts-3c spe. step 2 ? begin providing the values of the ?outbound? j1 byte message to the ?txpoh_n? input port. the procedure for applying the j1 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the j1 byte value into the outbound sts-3c spe data-stream if the user intends to externally insert the j1 byte into the outbound sts-3c spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 233 figure 36.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 234 figure 36: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 235 figure 36) is ?dashed? because controlling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should place the very first bit (e.g., the mo st significant bit) of the ?outbound? j1 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the j1 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. 2.2.7.3.5 support/handling of the c2 byte the transmit sts-3c poh processor block permits the user to control the value of the c2 byte by either of the following options. ? setting and controlling the ?outbound? c2 byte via software ? setting and controlling the ?outbound? c2 byte via the ?txpoh input port? the details and instructions for using eit her or these features are presented below. 2.2.7.3.5.1 setting and controlling the outbound c2 byte via software the transmit sts-3c poh processor block permits the user to specify the contents of the c2 byte, within the ?outbound? sts-3c spe via software command. the user can configure the transmit sts-3c poh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?0? into bit 2 (c2 insertion type) within the ?transmit sts-3c path ? sonet control register ? byte 0?, as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 236 transmit sts-3c path ? sonet control register ? byte 0 (address = 0x1983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 0 0 0 0 0 0 0 0 this step configures the transmit sts-3c poh proces sor block to read out the contents of the ?transmit sts-3c path ? transmit c2 byte value? register; and load this value into the c2 byte position within each ?outbound? sts-3c spe. step 2 ? write the desired byte value (for the outbound c2 byte) into the ?transmit sts-3c path ? transmit c2 byte value? register. the bit-format of this register is presented below. transmit sts-3c path ? transmit c2 byte value register (address = 0x199f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_c2_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.7.3.5.2 setting and controlling the outboun d c2 byte via the ?txpoh_n input port? the transmit sts-3c poh processor block permits the user to specify the contents of the c2 byte, within the ?outbound? sts-3c spe, via data applied to the ?txpoh_n? input pin. the user can configure the transmit sts-3c poh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 2 (c2 byte insertion type) within the ?transmit sts-3c path ? sonet control register ? byte 0?, as depicted below. transmit sts-3c path ? sonet control register ? byte 0 (address = 0x1983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 0 0 0 0 0 1 0 0 this step configures the transmit sts-3c poh proc essor block to use the ?txpoh_n? input port as the source for the c2 byte, within ea ch ?outbound? sts-3c spe. in this mode, the transmit sts-3c poh processor block will accept the value, corresponding to the c2 byte (via the ?txpoh_n? input port) and it will write this data into the c2 byte posit ion, within the ?outbound? sts-3c spe. step 2 ? begin providing the values of the ?outbound? c2 byte to the ?txpoh_n? input port. the procedure for applying the c2 byte to the ?txpoh_n? input port is presented below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 237 using the ?txpoh? i nput port to insert the c2 byte value into the outbound sts-3c spe data-stream if the user intends to externally insert the c2 byte into the outbound sts-3c spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 37. figure 37: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (infigure 37) is ?dashed? because cont rolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., wher e it will wait for 16 periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit th is ?wait state? and then place the very first bit (e.g., the most significant bit) of the ? outbound? c2 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the c2 byte is the third byte within the poh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the c2 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 238 2.2.7.3.6 support/handling of the f2 byte the transmit sts-3c poh processor block permits the user to control the value of the f2 byte by either of the following options. ? setting and controlling the ?outbound? f2 byte via software ? setting and controlling the ?outbound? f2 byte via the ?txpoh input port? the details and instructions for using eit her or these features are presented below. 2.2.7.3.6.1 setting and controlling the outbound f2 byte via software the transmit sts-3c poh processor bl ock permits the user to specify the contents of the f2 byte, within the ?outbound? sts-3c spe via software command. the user can configure the transmit sts-3c poh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?0? into bit 7 (f2 insertion type) within the ?transmit sts-3c path ? sonet control register ? byte 0?, as depicted below. transmit sts-3c path ? sonet control register ? byte 0 (address = 0x1983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 0 0 0 0 0 0 0 0 this step configures the transmit sts-3c poh proces sor block to read out the contents of the ?transmit sts-3c path ? transmit f2 byte value? register; and load this value into the f2 byte position within each ?outbound? sts-3c spe. step 2 ? write the desired byte value (for the outbound f2 byte) into the ?transmit sts-3c path ? transmit f2 byte value? register. the bit-format of this register is presented below. transmit sts-3c path ? transmit f2 byte value register (address = 0x19a3) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_f2_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.7.3.6.2 setting and controlling the outboun d f2 byte via the ?txpoh_n input port? the transmit sts-3c poh processor bl ock permits the user to specify the contents of the f2 byte, within the ?outbound? sts-3c spe, via data applied to the ?txpoh_n? input pin. the user can configure the transmit sts-3c poh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 7 (f2 byte insertion type) within the ?transmit sts-3c path ? sonet control register ? byte 0?, as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 239 transmit sts-3c path ? sonet control register ? byte 0 (address = 0x1983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 1 0 0 0 0 0 0 0 this step configures the transmit sts-3c poh proc essor block to use the ?txpoh_n? input port as the source for the f2 byte, within eac h ?outbound? sts-3c spe. in this mode, the transmit sts-3c poh processor block will accept the value, corresponding to the f2 byte (via the ?txpoh_n? input port) and it will write this data into the f2 byte posit ion, within the ?outbound? sts-3c spe. step 2 ? begin providing the values of the ?outbound? f2 byte to the ?txpoh_n? input port. the procedure for applying the f2 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the f2 byte value into the outbound sts-3c spe data-stream if the user intends to externally insert the f2 byte into the outbound sts-3c spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 38. figure 38: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in figure 38) is ?dashed? because cont rolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., wher e it will wait for 32 periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit th is ?wait state? and then place the very first bit (e.g.,
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 240 the most significant bit) of the ?outbound? f2 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the f2 byte is the fifth byte within the poh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the f2 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. figure 39 presents an illustration of the ?txpoh input interface? waveforms, when the ?external circuit? is writing the f2 byte into the ?txpoh input port?. figure 39 illustration of the ?txpoh i nput interface? waveforms, when th e ?external circuit? is writing the ?f2 byte? into the ?txpoh input port?. 2.2.7.3.7 support/handling of the h4 byte the transmit sts-3c poh processor block permits the user to control the value of the h4 byte by either of the following options. ? setting and controlling the ?outbound? h4 byte via software ? setting and controlling the ?outbound? h4 byte via the ?txpoh input port? the details and instructions for using eit her or these features are presented below. 2.2.7.3.7.1 setting and controlling the outbound h4 byte via software the transmit sts-3c poh processor block permits the user to specify the contents of the h4 byte, within the ?outbound? sts-3c spe via software command. the user can configure the transmit sts-3c poh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?0? into bit 0 (h4 insertion type) within the ?transmit sts-3c path ? sonet control register ? byte 1?, as depicted below. transmit sts-3c path ? sonet control register ? byte 1 (address = 0x1982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 0 this step configures the transmit sts-3c poh proces sor block to read out the contents of the ?transmit sts-3c path ? transmit h4 byte value? register; and load this value into the c2 byte position within each ?outbound? sts-3c spe. step 2 ? write the desired byte value (for the outbound h4 byte) into the ?transmit sts-3c path ? transmit h4 byte value? register. the bit-format of this register is presented below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 241 transmit sts-3c path ? transmit h4 byte value register (address = 0x19a7) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_h4_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.7.3.7.2 setting and controlling the outboun d h4 byte via the ?txpoh_n input port? the transmit sts-3c poh processor block permits the user to specify the contents of the h4 byte, within the ?outbound? sts-3c spe, via data applied to the ?txpoh_n? input pin. the user can configure the transmit sts-3c poh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 0 (f2 byte insertion type) within the ?transmit sts-3c path ? sonet control register ? byte 1?, as depicted below. transmit sts-3c path ? sonet control register ? byte 1 (address = 0x1982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 1 this step configures the transmit sts-3c poh proc essor block to use the ?txpoh_n? input port as the source for the h4 byte, within ea ch ?outbound? sts-3c spe. in this mode, the transmit sts-3c poh processor block will accept the value, corresponding to the h4 byte (via the ?txpoh_n? input port) and it will write this data into the h4 byte posit ion, within the ?outbound? sts-3c spe. step 2 ? begin providing the values of the ?outbound? h4 byte to the ?txpoh_n? input port. the procedure for applying the h4 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the h4 byte value into the outbound sts-3c spe data-stream if the user intends to externally insert the h4 byte into the outbound sts-3c spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 242 figure 40.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 243 figure 40: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 244 figure 40) is ?dashed? because controlling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., wher e it will wait for 40 periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit th is ?wait state? and then place the very first bit (e.g., the most significant bit) of the ? outbound? h4 byte onto the ?txpoh_n ? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the h4 byte is the sixth byte within the poh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the h4 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. figure 41 presents an illustration of the ?txpoh input interface? waveforms, when the ?external circuit? is writing the h4 byte into the ?txpoh input port?. figure 41 illustration of the ?txpoh i nput interface? waveforms, when th e ?external circuit? is writing the ?h4 byte? into the ?txpoh input port?. 2.2.7.3.8 support/handling of the z3 byte the transmit sts-3c poh processor block permits the user to control the value of the h4 byte by either of the following options. ? setting and controlling the ?outbound? z3 byte via software ? setting and controlling the ?outbound? z3 byte via the ?txpoh input port? the details and instructions for using eit her or these features are presented below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 245 2.2.7.3.8.1 setting and controlling the outbound z3 byte via software the transmit sts-3c poh processor bl ock permits the user to specify the contents of the z3 byte, within the ?outbound? sts-3c spe via software command. the user can configure the transmit sts-3c poh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?0? into bit 1 (z3 insertion type) within the ?transmit sts-3c path ? sonet control register ? byte 1?, as depicted below. transmit sts-3c path ? sonet control register ? byte 1 (address = 0x1982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 0 this step configures the transmit sts-3c poh proces sor block to read out the contents of the ?transmit sts-3c path ? transmit z3 byte value? register; and load this value into the z3 byte position within each ?outbound? sts-3c spe. step 2 ? write the desired byte value (for the outbound z3 byte) into the ?transmit sts-3c path ? transmit z3 byte value? register. the bit-format of this register is presented below. transmit sts-3c path ? transmit z3 byte value register (address = 0x19ab) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_z3_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.7.3.8.2 setting and controlling the outboun d z3 byte via the ?txpoh_n input port? the transmit sts-3c poh processor bl ock permits the user to specify the contents of the z3 byte, within the ?outbound? sts-3c spe, via data applied to the ?txpoh_n? input pin. the user can configure the transmit sts-3c poh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 1 (z3 byte insertion type) within the ?transmit sts-3c path ? sonet control register ? byte 1?, as depicted below. transmit sts-3c path ? sonet control register ? byte 1 (address = 0x1982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 1 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 246 this step configures the transmit sts-3c poh proc essor block to use the ?txpoh_n? input port as the source for the z3 byte, within eac h ?outbound? sts-3c spe. in this mode, the transmit sts-3c poh processor block will accept the value, corresponding to the z3 byte (via the ?txpoh_n? input port) and it will write this data into the z3 byte posit ion, within the ?outbound? sts-3c spe. step 2 ? begin providing the values of the ?outbound? z3 byte to the ?txpoh_n? input port. the procedure for applying the z3 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the z3 byte value into the outbound sts-3c spe data-stream if the user intends to externally insert the z3 byte into the outbound sts-3c spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 42. figure 42: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in figure 42) is ?dashed? because cont rolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., wher e it will wait for 48 periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit th is ?wait state? and then place the very first bit (e.g., the most significant bit) of the ?outbound? z3 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the z3 byte is the seventh byte within the poh.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 247 ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the z3 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. 2.2.7.3.9 support/handling of the z4 byte the transmit sts-3c poh processor block permits the user to control the value of the z4 byte by either of the following options. ? setting and controlling the ?outbound? z4 byte via software ? setting and controlling the ?outbound? z4 byte via the ?txpoh input port? the details and instructions for using eit her or these features are presented below. 2.2.7.3.9.1 setting and controlling the outbound z4 byte via software the transmit sts-3c poh processor bl ock permits the user to specify the contents of the z4 byte, within the ?outbound? sts-3c spe via software command. the user can configure the transmit sts-3c poh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?0? into bit 0 (z4 insertion type) within the ?transmit sts-3c path ? sonet control register ? byte 1?, as depicted below. transmit sts-3c path ? sonet control register ? byte 1 (address = 0x1982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 0 this step configures the transmit sts-3c poh proces sor block to read out the contents of the ?transmit sts-3c path ? transmit z4 byte value? register; and load this value into the z4 byte position within each ?outbound? sts-3c spe. step 2 ? write the desired byte value (for the outbound h4 byte) into the ?transmit sts-3c path ? transmit z4 byte value? register. the bit-format of this register is presented below. transmit sts-3c path ? transmit z4 byte value register (address = 0x19af) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_z4_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.7.3.9.2 setting and controlling the outboun d z4 byte via the ?txpoh_n input port? the transmit sts-3c poh processor bl ock permits the user to specify the contents of the z4 byte, within the ?outbound? sts-3c spe, via data applied to the ?txpoh_n? input pin. the user can configure the transmit sts-3c poh pr ocessor block to accomplish this by performing the following steps.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 248 step 1 ? write the value ?1? into bit 0 (z4 byte insertion type) within the ?transmit sts-3c path ? sonet control register ? byte 1?, as depicted below. transmit sts-3c path ? sonet control register ? byte 1 (address = 0x1982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 1 0 0 this step configures the transmit sts-3c poh proc essor block to use the ?txpoh_n? input port as the source for the z4 byte, within eac h ?outbound? sts-3c spe. in this mode, the transmit sts-3c poh processor block will accept the value, corresponding to the z4 byte (via the ?txpoh_n? input port) and it will write this data into the z4 byte posit ion, within the ?outbound? sts-3c spe. step 2 ? begin providing the values of the ?outbound? z4 byte to the ?txpoh_n? input port. the procedure for applying the z4 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the z4 byte value into the outbound sts-3c spe data-stream if the user intends to externally insert the z4 byte into the outbound sts-3c spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 43. figure 43: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 249 note: the ?txpohins_n? line (in figure 43) is ?dashed? because cont rolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., where it will wait for _ periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit this ?wait state? and then place the very first bit (e.g., the most significant bit) of the ?outbound? z4 byte onto the ?t xpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because t he z4 byte is the 8th byte within the poh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the h4 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. 2.2.7.3.10 support/handling of the z5 byte the transmit sts-3c poh processor block permits the user to control the value of the h4 byte by either of the following options. ? setting and controlling the ?outbound? z5 byte via software ? setting and controlling the ?outbound? z5 byte via the ?txpoh input port? the details and instructions for using eit her or these features are presented below. 2.2.7.3.10.1 setting and controlling the outbound z5 byte via software the transmit sts-3c poh processor bl ock permits the user to specify the contents of the z5 byte, within the ?outbound? sts-3c spe via software command. the user can configure the transmit sts-3c poh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?0? into bit 0 (z5 insertion type) within the ?transmit sts-3c path ? sonet control register ? byte 1?, as depicted below. transmit sts-3c path ? sonet control register ? byte 1 (address = 0x1982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 x this step configures the transmit sts-3c poh proces sor block to read out the contents of the ?transmit sts-3c path ? transmit z5 byte value? register; and load this value into the z5 byte position within each ?outbound? sts-3c spe. step 2 ? write the desired byte value (for the outbound z5 byte) into the ?transmit sts-3c path ? transmit z5 byte value? register. the bit-format of this register is presented below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 250 transmit sts-3c path ? transmit z5 byte value register (address = 0x19b3) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_z5_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.7.3.10.2 setting and controlling the outboun d z5 byte via the ?txpoh_n input port? the transmit sts-3c poh processor bl ock permits the user to specify the contents of the z5 byte, within the ?outbound? sts-3c spe, via data applied to the ?txpoh_n? input pin. the user can configure the transmit sts-3c poh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 0 (z5 byte insertion type) within the ?transmit sts-3c path ? sonet control register ? byte 1?, as depicted below. transmit sts-3c path ? sonet control register ? byte 1 (address = 0x1982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 1 0 0 0 this step configures the transmit sts-3c poh proc essor block to use the ?txpoh_n? input port as the source for the z5 byte, within eac h ?outbound? sts-3c spe. in this mode, the transmit sts-3c poh processor block will accept the value, corresponding to the z5 byte (via the ?txpoh_n? input port) and it will write this data into the z5 byte posit ion, within the ?outbound? sts-3c spe. step 2 ? begin providing the values of the ?outbound? z5 byte to the ?txpoh_n? input port. the procedure for applying the z5 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the z5 byte value into the outbound sts-3c spe data-stream if the user intends to externally insert the z5 byte into the outbound sts-3c spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 44
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 251 figure 44: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in figure 44) is ?dashed? because cont rolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., where it will wait for _ periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit this ?wait state? and then place the very first bit (e.g., the most significant bit) of the ?outbound? z5 byte onto the ?t xpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the z5 byte is the ninth byte within the poh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the z5 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. 2.2.7.3.11 pointer-adjustment/ndf options forcing pointer adjustments and ndf events via software the ?transmit sts-3c poh processor? block permits the user to insert pointer adjustments or ndf events into the ?outbound? sts-3c data stream . specifically, the transmit sts-3c poh processor block permits the user to implement the following ?pointer-related? features. ? to force the pointer to shift to an ?arbitrary value? ? to configure the transmit sts-3c poh processor block to only insert pointer-adjustment or ndf events, if no pointer-adjustment (ndf or otherwise) events have occurred within the last three (3) sts-3c framing periods.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 252 ? to force a ?positive-stuff? pointer-adjustment event ? to force a ?negative-stu ff? pointer-adjustment event ? to force a single ndf event ? to force a continuous ndf event ? to read out and determine the current ?pointer-v alue? within the outbound sts-3c data-stream. the procedure for implementing each of these ?pointer-related? events is presented below. forcing the pointer to shift to an arbitrary value the transmit sts-3c poh processor block permits the user to assign the arbitrary value to the pointer bytes, within the outbound sts-3c spe data-stream. the user can invoke this feature by executing the following steps. step 1 ? write the appropriate ?ndf?, ?ss? and h1, h2 pointer values into the ?transmit sts-3c path ? transmit arbitrary h1 pointer? register, and the ?transmit sts-3c path ? transmit arbitrary h2 pointer? register. the bit-format for these two registers is presented below. transmit sts-3c path ? transmit arbitrary h1 byte pointer register (address = 0x19bf) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 ndf bits ss bits h1 pointer value r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 transmit sts-3c path ? transmit arbitrary h2 byte pointer register (address = 0x19c3) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 h2 pointer value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 step 2 ? induce a ?0 to 1 transition? in bit 5 (pointer force) within the ?transmit sts-3c path ? transmit path control register, as depicted below. transmit sts-3c path ? transmit path control register (address = 0x19b7) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused pointer force check stuff insert negative stuff insert positive stuff insert continuous ndf events insert single ndf event r/o r/o r/w r/w w w r/w r/w 0 0 0 ->1 0 0 0 0 0 once the user induces this ?0 to 1 transition? in bit 5, then the following events will occur, within the very next ?outbound? sts-3c frame. ? the ndf bits, within the h1 byte, will be set to the va lue written into bits 4 through 7 (ndf bits) within the ?transmit sts-3c path ? transmit ar bitrary h1 byte pointer register.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 253 ? the ?ss? bits, within the h1 byte, will be set to t he value written into bits 2 and 3 (ss bits) within the ?transmit sts-3c path ? transmit ar bitrary h1 byte pointer register. ? the 10-bit pointer value (within bits 7 and 8, within the h1 byte, and all eight bits within the h2) will be set to the values written into bits 1 and 0 (h1 pointer) within the ?transmit sts-3c path ? transmit arbitrary h1 byte pointer? register, and bits 7 through 0 (h2 pointer value) within the ?transmit sts-3c path ? transmit arbitrary h2 byte pointer? register. 2.2.7.3.11.1 forcing positive-stuff poin ter adjustment events via software the transmit sts-3c poh processor block permits the us er to insert a ?positive-stuff? pointer adjustment event into the outbound sts-3c data-stream. this can be ac complished by inducing a ?0 to 1? transition in bit 2 (insert positive stuff) within the ?transmit sts-3c path ? transmit path control? register, as depicted below. transmit sts-3c path ? transmit path control register (address = 0x19b7) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused pointer force check stuff insert negative stuff insert positive stuff insert continuous ndf events insert single ndf event r/o r/o r/w r/w w w r/w r/w 0 0 0 0 0 0 -> 1 0 0 once the user induces this ?0 to 1 transition? in bit 2, then the following events will occur. ? a ?positive-stuff? will occur (e.g., a single stuf f byte will be inserted into the sts-3c data-stream, immediately after the h3 byte position). ? the ?i? bits, within the h1 and h2 bytes will be inve rted (to denote an ?incrementing? pointer adjustment) event. ? after the ?positive-stuff? event, t he pointer (consisting of the h1 and h2 bytes) will be incremented by ?1? and will be used as the new pointer from this point on. note: the contents of bit 2 (insert positive stuff) will be automatically cleared after the user has written a ?1? into this bit-field. hence, there is no need for the user to go back and write a ?0? into this bit-field. 2.2.7.3.11.2 forcing negative-stuff poin ter adjustment events via software the transmit sts-3c poh processor block permits the us er to insert a ?positive-stuff? pointer adjustment event into the outbound sts-3c data-stream. this ca n be accomplished by inducing a ?0 to 1 transition? within bit 3 (insert negative stuff) within the ?transmi t sts-3c path ? transmit path control? register; as depicted below. transmit sts-3c path ? transmit path control register (address = 0x19b7) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused pointer force check stuff insert negative stuff insert positive stuff insert continuous ndf events insert single ndf event r/o r/o r/w r/w w w r/w r/w 0 0 0 0 0 ->1 0 0 0 once the user induces a ?0 to 1? transition in bit 3, then the following events will occur.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 254 ? a ?negative-stuff? will occur (e.g., a single payload byte will be inserted into the ?h3 byte? position, within the outbound sts-3c data-stream). ? the ?d? bits, within the h1 and h2 bytes will be inverted (to denote a ?decrementing? pointer-adjustment event). ? the contents of the h1 and h2 bytes will be decrem ented by ?1? and will be used as the new pointer from this point on. note: the contents of bit 3 (insert negative stu ff) will be automatically cleared after the user has written a ?1? into this bit-field. hence, there is no need for the user to go back and write a ?0? into this bit-field. 2.2.7.3.11.3 forcing a singl e ndf event via software the transmit sts-3c poh processor block permits the user to force a single ndf event into the outbound sts-3c data-stream. this can be acco mplished by executing the following steps. step 1- write the new ?desired? pointer value into bits 1 and 0 (h1 pointer value) within the ?transmit sts-3c path ? transmit arbitrary h1 pointer register; and bits 7 through 0 (h2 pointer value) within the ?transmit sts-3c path ? transmit arbitrary h2 pointer register. the bit-format of these two registers (with the relevant bit-fields shaded) is presented below. transmit sts-3c path ? transmit arbitrary h1 byte pointer register (address = 0x19bf) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 ndf bits ss bits h1 pointer value r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 transmit sts-3c path ? transmit arbitrary h2 byte pointer register (address = 0x19c3) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 h2 pointer value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 step 2 ? induce a ?0 to 1 transition? in bit 0 (insert single ndf event) within the ?transmit sts-3c path ? transmit path control? register; as depicted below. transmit sts-3c path ? transmit path control register (address = 0x19b7) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused pointer force check stuff insert negative stuff insert positive stuff insert continuous ndf events insert single ndf event r/o r/o r/w r/w w w r/w r/w 0 0 0 0 0 0 0 0->1 once the user induces this ?0 to 1 transition? in bit 0, then the following events will occur. ? the ?n? bits, in the h1 byte (within the very next outbound sts-3c frame) will be set to the value ?1001?.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 255 ? the ten pointer value bits (within the h1 and h2 bytes) will be set to the value that was written into the ?transmit sts-3c path ? transmit arbi trary h1 byte pointer? and ?transmi t sts-3c path ? transmit arbitrary h2 byte pointer? registers; during step 1. ? afterwards, the n-bits will resume their normal valu e of ?0110?, and this new po inter value will be used as the new pointer, from this point on. note: once the user writes a ?1? into bit 0 (insert single ndf event), the xrt94l33 will aut omatically clear this bit- field. hence, there is no need to s ubsequently reset this bit-field to ?0?. 2.2.8 t ransmit sonet poh processor block ( for atm/ppp over sts-3 a pplications ) all outbound atm cells that exit the transmit atm cell processor block w ill be routed to the transmit sonet poh processor block, wher e they will be mapped into either sts-1 spes. likewise, all outbound ppp packets that exit the tr ansmit ppp packet processor block will be routed to the transmit sonet poh processor block, where t hey will be mapped into sts-1 spes. t he purpose of the transmit sonet poh processor block is to accomplish the following. ? to accept atm cells from the transmit atm cell processor block and to map these cells into sts-1 spe (synchronous payload envelope), or ? to accept ppp packets from the transmit ppp packet processor block and to map these packets into sts-1 spes ? to compute and insert the b3 (path bip-8) byte ? to deliberately transmit an sts-1 spe with an erred b3 byte (for testing purposes) ? to source the j1, c2, g1, f2, h4, z3, z4 and z5 bytes. ? to automatically transmit the rdi-p (path ? remote defect) indicator whenever (and for the duration that) the corresponding receive sonet poh processor block declares the ai s-p, lop-p, uneq-p, tim-p or plm-p defect conditions. ? to automatically transmit the rdi-p indicator wh enever (and for the duration that) the corresponding receive atm cell processor block declares the lcd defect condition. ? to transmit the rdi-p indicator upon software control. ? to automatically transmit the rei-p (path ? remo te error) indicator anytime the corresponding receive sonet poh processor block detects b3 byte e rrors in its incoming sts-1 spe data-stream. ? to transmit the rei-p indicator upon software control. ? to transmit the ais-p (path ? alarm indi cation signal) indicator upon software control. ? to permit the user to transmit ei ther 1 byte, 16 byte or 64 byte path trace messages to the remote pte. ? to force ?positive-stuff? pointer ad justments in the outbound sts-1 data-stream. ? to force ?negative-stuff? pointer adju stments in the outbound sts-1 data-stream. ? to force single and continuous ndf (new data flag) events into the outbound sts-1 data-stream ? to route its output data to the transmit st s-1 toh processor block for further processing. figure 46presents an illustration of the block diagram of the xrt94l33 mapper ic, with the ?transmit sonet poh processor? block highlighted.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 256 figure 45: illustration of the functi onal block diagram of the xrt94l 33 mapper ic, with the transmit sonet poh processor block high-lighted transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3 toh processor block receive sts-3 toh processor block transmit sts-3 toh processor block transmit sts-3 toh processor block receive sonet poh processor block receive sonet poh processor block transmit sonet poh processor block transmit sonet poh processor block sts-3/12 telecom bus interface block sts-3/12 telecom bus interface block sts-3/12 pecl interface block sts-3/12 pecl interface block sts-3/12 cdr block sts-3/12 cdr block xrt94l33 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block from channels 1 and 2 to channels 1 and 2 some background information on the path overhead (poh) bytes for sts-1 applications, the size of the spe is 9 rows by 261 byte columns. figure 46 presents a simple illustration of the sts-1 spe. figure 46: simple illustration of the sts-1 spe in each case, the first byte column within an sts- 1 spe is referred to as the path overhead (poh). therefore, in all, the poh consists of a total of nine (9) bytes. each of these poh bytes is briefly described below. j1 ? the path trace byte b3 ? the path bip-8 byte c2 ? the payload label byte g1 ? the path status byte f2 ? the path user channel byte h4 ? the multi-frame indicator (not used for atm and ppp applications) z3, z4 and z5 ? growth bytes the remainder of this section describes how the tr ansmit sonet poh processor block handles these poh bytes. the operation of the ?transmit sonet poh proce ssor? block is discussed in some detail below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 257 2.2.8.1 receiving atm cell data from the transmit atm cell processor block the transmit sonet poh processor bl ock receives atm cell data from the transmit atm cell processor block; and maps this data into an sts-1 spe. as the transmit sonet poh processor block receiv es this atm cell data from the transmit atm cell processor block, it will perfo rm the following functions. ? it will map these atm cells into the payload bytes, within the sts-1 spe. ? compute and insert the b3 byte ? source (per user configuration) the j1, c2, g1, f2, h4, z3, z4 and z5 bytes ? to (automatically or upon softw are command) transmit the rdi-p (p ath ? remote defect indicator) indicator ? to (automatically or upon software command) transmit the rei-p (path ? remote error indicator) indicator ? to (upon software command) transmit the ai s-p (path ? alarm indication signal) indicator ? to (upon software command) force pointer-adjustment or ndf (new data flag) events into the outbound sts-1 data-stream. each of these functions is described in detail below. 2.2.8.2 computation and insertion of the path bip-8 (b3) byte the transmit sonet poh processor block creates st s-1 spe data and computes a bip-8 value over this sts-1 spe. the results of this calc ulation are inserted into the b3 byte -position within the very next sts-1 spe. the remote pte (path terminating equipment) will use this byte, in order to perform error- checking/detection on the incoming sts-1 spe data that it receives. transmission of erred b3 bytes in the outbound sts-1 data-stream the transmit sonet poh processor block permits the user to insert errors into the ?b3 bytes?, within the outbound sts-1 spe data-stream. the user can accomplish this by writing a non-zero va lue into the ?transmit sonet path ? transmitter b3 byte error mask? register. the ?transmit sonet po h processor block will perf orm an xor operation with the contents of the ?outbound? b3 byte, and the contents of this register. the results of this calculation are written back into the b3 byte position, within the outbound sts-1 spe data-stream. the bit-format of the ?transmit sonet path ? transm it b3 byte error mask? re gister is presented below. transmit sonet path ? transmitter b3 byte error mask register (address = 0xn997) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_b3_byte_mask[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 note: for normal (e.g., un-erred) operation, the user should ensure that this register is set to ?0x00? (the default value).
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 258 2.2.8.3 transmission of path-alarm conditions the transmit sonet poh processor bloc k supports the following functions. ? transmitting the ais-p pattern (under software control) ? transmitting the rdi-p indicator ( automatically and under software control) ? transmitting the rei-p indicator ( automatically and under software control) each of these operations is discussed in detail below. 2.2.8.3.1 transmission of the ais-p pattern the transmit sonet poh processor block can be config ured to generate and transmit the ais-p (path ais) indicator to the remote pte, under software control. the user can accomplish this by setting bit 0 (transmit ais-p enable) within the ?transmit sonet path ? sonet control register ? byte 0? to ?1?, as depicted below. transmit sonet path ? sonet control register ? byte 0 (address = 0xn983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 0 0 0 0 0 0 0 1 once the user executes this step, then the ?trans mit sonet poh processor? block will do the following. ? it will set all bytes, within the sts-1 spe to an ?all ones? pattern. ? it will set the h1, h2 and h3 bytes (w ithin the toh) to an ?all ones? pattern. please note that whenever the user configures the tr ansmit sonet poh processor block to transmit the ais-p indicator, then no atm cells or ppp packe ts will be transmitted to the remote terminal. 2.2.8.3.2 transmission of the rdi-p indicator the transmit sonet poh processor block can be c onfigured to transmit the rdi-p indicator either automatically, upon software control or via the ?txp oh_n? external input port as described below. 2.2.8.3.2.1 configuring the tran smit sonet poh processor block to automatically transmit the rdi-p indicator the user can configure the transmit sonet poh proc essor block to automatically transmit the rdi-p indicator whenever the corresponding receive sonet poh processor block declares a plm-p (path ? payload label mismatch), uneq-p (path ? unequipped), lop-p (path ? loss of pointer), ais-p, tim-p (path - trace identificat ion mismatch), and lcd-p (path ? loss of cell delineation) condition. the procedure for configuring the transmit sonet poh processor block to automatically transmit the rdi-p indicator, for each of the above-ment ioned defects is presented below. 2.2.8.3.2.2 configuring the tran smit sonet poh processor block to automatically transmit rdi- p, in response to declaration of the plm-p condition the user can configure the transmit sonet poh proc essor block to automatically transmit the rdi-p indicator, in response to the corresponding rece ive sonet poh processor block declaring the plm-p condition, by executing the following steps.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 259 step 1 ? write the value [0, 0] into bits 3 and 4 (rdi-p insertion type[1, 0]) within the ?transmit sonet path ? sonet control register ? byte 0? as depicted below. transmit sonet path ? sonet control register ? byte 0 (address = 0xn983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 this step configures the ?transmit sonet poh processor? block to automatically set bits 5 through 7 (of the g1 byte) within the outbound sts-1 spe; to the appropriate ?rdi-p value? based upon receive conditions as detected by the corresponding ?recei ve sonet poh processor? block. step 2 ? write the appropriate value into bits 3 through 1 (plm-p rdi-p code[2:0]) within the ?transmit sonet path ? rdi-p control re gister ? byte 2? as illustrated below. transmit sonet path ? rdi-p control register ? byte 2 (address = 0xn9c9) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lcd-p rdi-p code[2:0] transmit rdi-p upon lcd-p plm-p rdi-p code[2:0] transmit rdi-p upon plm-p r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 x x x 0 by writing this particular value into these three bit-fiel ds, the user is specifying the value that the ?transmit sonet poh processor? block will set the rdi-p bit-fiel ds (within the ?outbound g1 byte) to, whenever the corresponding receive sonet poh processo r block declares the plm-p condition. step 3 ? set bit 0 (transmit rdi-p upon plm-p) within the ?transmit sonet path ? rdi-p control register ? byte 2? to ?1?, as illustrated below. transmit sonet path ? rdi-p control register ? byte 2 (address = 0xn9c9) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lcd-p rdi-p code[2:0] transmit rdi-p upon lcd-p plm-p rdi-p code[2:0] transmit rdi-p upon plm-p r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 x x x 1 this step configures the transmit sonet poh processor block to automatically tran smit the rdi-p indicator (per the values written into bits 3 through 1; within this register), anytime the corresponding receive sonet poh processor block detects the ?plm-p? condition.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 260 2.2.8.3.2.3 configuring the tran smit sonet poh processor block to automatically transmit rdi- p, in response to declaration of the uneq-p condition the user can configure the transmit sonet poh proc essor block to automatically transmit the rdi-p indicator, in response to the corresponding receive sonet poh processor block declaring the uneq-p condition, by executing the following steps. step 1 ? write the appropriate value into bits 3 through 1 (uneq-p rdi-p code[2:0]) within the ?transmit sonet path ? rdi-p condition re gister ? byte 1, as illustrated below. transmit sonet path ? rdi-p control register ? byte 1 (address = 0xn9ca) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 tim-p rdi-p code[2:0] transmit rdi-p upon tim-p uneq-p rdi-p code[2:0] transmit rdi-p upon uneq-p r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 x x x 0 by writing this particular value into these bit-fields the user is specifying the value that the ?transmit sonet poh processor? block will set the rdi-p bit-fields (within the g1 byte of outbound sts-1 frame) to whenever the corresponding receive sonet poh proces sor block declares the uneq-p condition. step 2 ? set bit 0 (transmit rdi-p upon uneq-p) wi thin the ?transmit sonet path ? rdi-p control register ? byte 1? to ?1?, as illustrated below. transmit sonet path ? rdi-p control register ? byte 1 (address = 0xn9ca) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 tim-p rdi-p code[2:0] transmit rdi-p upon tim-p uneq-p rdi-p code[2:0] transmit rdi-p upon uneq-p r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 x x x 1 this step configures the transmit sonet poh processo r block to transmit the rdi-p indicator (per the values written into bits 3 through 1, within this register); anytime the corr esponding ?receive sonet poh processor? block declares the ?uneq-p? condition. 2.2.8.3.2.4 configuring the tran smit sonet poh processor block to automatically transmit rdi- p, in response to declaration of the lop-p condition the user can configure the transmit sonet poh proc essor block to automatically transmit the rdi-p indicator, in response to the corresponding rece ive sonet poh processor block declaring the lop-p condition, by executing the following steps.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 261 step 1 ? write the appropriate value into bits 7 through 5 (lop-p rdi-p code[2:0]) within the ?transmit sonet path ? rdi-p control re gister ? byte 0?; as illustrated below. transmit sonet path ? rdi-p control register ? byte 0 (address = 0xn9cb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lop-p rdi-p code[2:0] transmit rdi-p upon lop-p ais-p rdi-p code[2:0] transmit rdi-p upon ais-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 0 0 0 0 0 by writing this particular value into these three bit-fi elds, the user is specifying the value that the transmit sonet poh processor block will set the rdi-p bit-fiel ds (in the g1 byte, within the ?outbound? sts-1 data- stream) whenever the corresponding receive sonet po h processor block declares the lop-p condition. step 2 ? set bit 4 (transmit rdi-p upon lop-p) with in the ?transmit sonet path ? rdi-p control register ? byte 0? to ?1?; as illustrated below. transmit sonet path ? rdi-p control register ? byte 0 (address = 0xn9cb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lop-p rdi-p code[2:0] transmit rdi-p upon lop-p ais-p rdi-p code[2:0] transmit rdi-p upon ais-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 1 0 0 0 0 this step configures the transmit sonet poh processor block to automatically tran smit the rdi-p indicator (per the values written into bits 3 through 1, within this register); anytime the corresponding ?receive sonet poh processor? block declares the ?lop-p? condition. 2.2.8.3.2.5 configuring the tran smit sonet poh processor block to automatically transmit rdi- p, in response to declaration of the ais-p condition the user can configure the transmit sonet poh pr ocessor block to automatically transmit the rdi-p indicator, in response to the corresponding receive so net poh processor declaring the ais-p condition, by executing the following steps. step 1 ? write the appropriate value into bits 3 through 1 (ais-p rdi-p code[2:0]) within the ?transmit sonet path ? rdi-p control re gister ? byte 0?; as illustrated below. transmit sonet path ? rdi-p control register ? byte 0 (address = 0xn9cb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lop-p rdi-p code[2:0] transmit rdi-p upon lop-p ais-p rdi-p code[2:0] transmit rdi-p upon ais-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 1 x x x 0 by writing this particular value into these three bit-fi elds, the user is specifying the value that the transmit sonet poh processor block will set the rdi-p bit-fiel ds (in the g1 byte, within the ?outbound? sts-1 data- stream) whenever the corresponding receive sonet po h processor block declares the ais-p condition.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 262 step 2 ? set bit 0 (transmit rdi-p upon ais-p) within the ?transmit sonet path ? rdi-p control register ? byte 0?, as illustrated below. transmit sonet path ? rdi-p control register ? byte 0 (address = 0xn9cb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lop-p rdi-p code[2:0] transmit rdi-p upon lop-p ais-p rdi-p code[2:0] transmit rdi-p upon ais-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 1 x x x 1 this step configures the transmit sonet poh processor block to automatically tran smit the rdi-p indicator (per the values written into bits 3 through 1, within this register); anytime the corresponding ?receive sonet poh processor? block declares the ?ais-p? condition. 2.2.8.3.2.6 configuring the tran smit sonet poh processor block to automatically transmit rdi- p, in response to declaration of the tim-p condition the user can configure the transmit sonet poh pr ocessor block to automatically transmit the rdi-p indicator, in response to the corresponding rece ive sonet poh processor block declaring the tim-p condition, by executing the following steps. step 1 ? write the appropriate value into bits 7 through 5 (tim-p rdi-p code[2:0]) within the ?transmit sonet path ? rdi-p condition re gister ? byte 1; as illustrated below. transmit sonet path ? rdi-p control register ? byte 1 (address = 0xn9ca) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 tim-p rdi-p code[2:0] transmit rdi-p upon tim-p uneq-p rdi-p code[2:0] transmit rdi-p upon uneq-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 0 x x x x by writing this particular value into these bit-fields the user is specifying the value that the ?transmit sonet poh processor? block will set the rdi -p bit-fields (within the g1 byte of the outbound sts-1 frame) to whenever the corresponding receive sonet poh pr ocessor block declares the tim-p condition. step 2 ? set bit 4 (transmit rdi-p upon tim-p) within the ?transmit sonet path ? rdi-p control register ? byte 1?; to ?1? as illustrated below. transmit sonet path ? rdi-p control register ? byte 1 (address = 0xn9ca) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 tim-p rdi-p code[2:0] transmit rdi-p upon tim-p uneq-p rdi-p code[2:0] transmit rdi-p upon uneq-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 1 x x x x this step configures the transmit sonet poh processo r block to transmit the rdi-p indicator (per the values written into bits 3 through 1, within this register); anytime the corr esponding ?receive sonet poh processor? block declares the ?tim-p? condition.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 263 2.2.8.3.2.7 configuring the tran smit sonet poh processor block to automatically transmit rdi- p, in response to declaration of the lcd-p condition the user can configure the transmit sonet poh pr ocessor block to automatically transmit the rdi-p indicator, in response to the corresponding rece ive sonet poh processor block declaring the lcd-p condition, by executing the following steps. step 1- write the appropriate value into bit 7 through 5 (lcd-p rdi-p code[2:0]) within the ?transmit sonet path ? rdi-p control register ? byte 2? as illustrated below. transmit sonet path ? rdi-p control register ? byte 2 (address = 0xn9c9) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lcd-p rdi-p code[2:0] transmit rdi-p upon lcd-p plm-p rdi-p code[2:0] transmit rdi-p upon plm-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 0 x x x 0 by writing this particular value into these three bit-fiel ds, the user is specifying the values that the ?transmit sonet poh processor? block will set the rdi-p bit-fields (withi n the outbound g1 byte ) to, whenever the corresponding receive sonet poh processo r block declares the lcd-p condition. step 2 ? set bit 4 (transmit rdi-p upon lcd-p) with in the ?transmit sonet path ? rdi-p control registers ? byte 2? to ?1?, as illustrated below. transmit sonet path ? rdi-p control register ? byte 2 (address = 0xn9c9) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 lcd-p rdi-p code[2:0] transmit rdi-p upon lcd-p plm-p rdi-p code[2:0] transmit rdi-p upon plm-p r/w r/w r/w r/w r/w r/w r/w r/w x x x 1 x x x 0 2.2.8.3.2.8 configuring the transm it sonet poh processor block to transmit the rdi-p indicator, upon software control the user can configure the transmit sonet poh pr ocessor block to transmit the rdi-p (per software command) by executing the following steps. step 1 ? write the value ?[0, 1]? into bits 3 and 4 (rdi-p insertion type[1:0]) within the ?transmit sonet path ? sonet control register ? byte 0?, as depicted below. transmit sonet path ? sonet control register ? byte 0 (address = 0xn983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 0 0 0 0 1 0 0 0 this step configures the ?transmit sonet poh processo r? block to automatically read out the contents of bits 3 through 1 (of the ?transmit sonet path ? g1 byte value? register); and writ e the value of these bits
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 264 into bits 5 through 7 (of the g1 byte) within the ?o utbound? sts-1 spe. the bit-format of the ?transmit sonet path ? g1 byte value? register (with t he appropriate bits ?shaded?) is presented below. transmit sonet path ? transmit g1 byte value register (address = 0xn99f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_g1_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 x x x 0 in this mode, the user can transmit an ?un-erred? in dicator by setting bits 3 through 1 (within the transmit sonet path ? transmit g1 byte value? register) to [0 , 0, 0]. conversely, the user can now transmit an ?erred? indicator by setting bits 3 through 1 (within the ?transmit sonet path ? transmit g1 byte value? register) to some value other than [0, 0, 0]. configuring the transmit sonet poh processor block to transmit the rdi-p indicator, via the ?txpoh_n? input port. the user can configure the transmit sonet poh processo r block to transmit the rdi -p (per external input port) by executing the following steps. step 1 ? write the value ?[1, 0]? into bits 3 and 4 (rdi-p insertion type[1:0]) within the ?transmit sonet path ? sonet control register ? byte 0?, as depicted below. transmit sonet path ? sonet control register ? byte 0 (address = 0xn983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 0 0 0 1 0 0 0 0 this step configures the ?transmit sonet poh processo r? block to set the value of the rdi-p bit-fields (within the outbound sts-1 spe) based upon the data that it receives via t he ?txpoh_n? input port. in this mode, the transmit sonet poh processor block will accept the value, corresponding to the rdi-p bit-fields (via the ?txpoh_n input port?) and it will write this data into the ?outbound? sts-1 spe data-stream. step 2 ? begin providing the values of the ?outbound? rdi-p bit-fields to the ?txpoh_n? input port. the procedure for applying the rdi-p bit-values to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the rdi-p bit valu es into the outbound sts-1 spe data-stream if the user intends to externally in sert the rdi-p bits into the outbound sts-1 spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 47.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 265 figure 47: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in figure 47) is ?dashed? because cont rolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., where it waits for 25 periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit this ?wait state? and then place the very first bit of the ?outbound? rdi-p bit-fields onto the ?txpoh_n? input pi n, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sonet poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the g1 by te is the 4th byte within the poh; and bit 7 (which is the very first rdi-p bit to be latched into the external in put interface is the second bit within the g1 byte to be processed). ? afterwards, the ?external circuit? should serially pl ace the remaining two bits (of the rdi-p bits) onto the ?txpoh_n? input pin, upon each of the next two falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. figure 48 presents an illustration of the ?txpoh input interface? waveforms, when the ?external circuit? is writing the rdi-p bits into the ?txpoh input port?. figure 48 illustration of the ?txpoh i nput interface? waveforms, when th e ?external circuit? is writing the ?rdi-p bits? into the ?txpoh input port?.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 266 2.2.8.3.3 transmission of the rei-p indicator the transmit sonet poh processor block can be confi gured to transmit the rei-p indicator either (1) automatically, (2) upon software command or (3) via the ?txpoh_n? input port as described below. 2.2.8.3.3.1 configuring the tran smit sonet poh processor block to automatically transmit the rei-p indicator the user can configure the transmit sonet poh proc essor block to automatically transmit the rei-p indicator whenever the corresponding receive sonet poh processor block detects at least one b3 byte error within its incoming sts-1 spe data-stream. the user can configure the transmit sonet poh proc essor block to automatically transmit the rei-p indicator, in response to detection of b3 by te errors, by executing the following steps. step 1 ? write the value [0, 0] into bits 5 and 6 (rei-p insertion type[1, 0]) within the ?transmit sonet path ? sonet control register ? byte 0? as depicted below. transmit sonet path ? sonet control register ? byte 0 (address = 0xn983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type c2 byte auto insert mode enable transmit ais-p enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 this step configures the ?transmit sonet poh processor? block to automatically set bits 1 through 4 (of the g1 byte) within the ?outbound? sts-1 spe to the approp riate rei-p value, based upon receive conditions as detected by the corresponding rece ive sonet poh processor block. step 2 ? indicate whether the rei-p value (transmitted to the remote pte) reflects the number of bits (within the b3 byte) that are in e rror, or the number of erred sts-1 spe that have been detected by the corresponding receive sonet poh processor block. the xrt94l33 permits the user to (1) flag b3 byte erro rs, and (2) to transmit the resulting rei-p value (back out to the remote pte) by the following means. ? by flagging and reporting the number of bits (within the b3 byte) that have be determined to be in error, within a given sts-1 spe. ? by flagging and reporting whethe r or not the corresponding receive sonet poh processor block is currently receiving erred sts-1 spe. the user can choose between these two options by writ ing the appropriate value into bit 0 (b3 error type) within the receive sonet path ? control register ? byte 0?; as illustrated below. receive sonet path ? control register ? byte 0 (address = 0x1183) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused check stuff rdi-p type rei-p error type b3 error type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 x
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 267 setting this bit-field to ?0? configures the transmit sonet poh processor block to set the rei-p bit-fields (within the g1 byte of the ?outboun d? sts-1 spe); to a value the reflects the number of bits (within the b3 byte) that were determined to be in error (within the most recently received st s-1 spe) by t he corresponding receive sonet poh processor block. in this case, t he rei-p bit-fields can range in value from ?0? (for no b3 bit errors) to ?8? (for all b3 bits being in error). setting this bit-field to ?1? configures the transmit sonet poh processor block to set the rei-p bit-fields (within the g1 byte of the ?outbound?st s-1 spe); to a value that indicates wh ether or not at l east one b3 byte error was detected within the most recently received st s-1 spe; by the corres ponding receive sonet poh processor block. in this mode, the transmit sonet poh processor block will set the ?rei-p? bit-fields (within the outbound sts-1 spe) to ?0 ? if the corresponding ?receive sonet poh processor? block is not detecting any b3 byte errors, in its incoming sts- 1 data-stream. conversely, the transmit sonet poh processor block will set the ?rei-p? bi t-fields (within the ?outbound? sts- 1 spe) to ?1? if the corresponding receive sonet poh processor bl ock receives an sts-1 spe that contains a b3 byte error. 2.2.8.3.3.2 configuring the transm it sonet poh processor block to transmit the rei-p indicator, upon software control the user can configure the transmit sonet poh proc essor block to transmit the rei-p indicator (per software command) by executing the following steps. step 1- write the value ?[0, 1]? into bits 5 and 6 (rei-p insertion type[1:0]) within the ?transmit sonet path sonet control register ? byte 0?; as depicted below. transmit sonet path ? sonet control register ? byte 0 (address = 0xn983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type c2 byte auto insert mode enable transmit ais-p enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 1 0 0 0 0 0 this step configures the ?transmit sonet poh processo r? block to automatically read out the contents of bits 4 through 7 (of the transmit sonet path ? g1 byte va lue? register) and write the value of these bits into bits 1 through 4 (of the g1 byte) within the ?outbound? sts-1 spe. the bit-format of the ?transmit sonet path ? g1 byte value? register (with the appropriate bits ?shaded?) is presented below. transmit sonet path ? transmit g1 byte value register (address = 0xn99f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_g1_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 x x x 0 in this mode, the user can transmit an ?un-erred? rei-p value by setting bits 4 through 7 (within the transmit sonet path ? transmit g1 byte value? register) to [0, 0, 0, 0]. conversely, the user can transmit an ?erred? rei-p value by setting bits 4 through 7 (within the trans mit sonet path ? transmit g1 byte value? register) to some value between 1 and 8.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 268 2.2.8.3.3.3 configuring the transm it sonet poh processor block to transmit the rei-p indicator, via the ?txpoh_n? input port the user can configure the transmit sonet poh proces sor block to transmit the rei-p (per the external input port) by executing the following steps. step 1 ? write the value [1, 0] into bits 3 and 4 (rei-p insertion type[1:0]) within the ?transmit sonet path ? sonet control register ? byte 0? as depicted below. transmit sonet path ? sonet control register ? byte 0 (address = 0xn983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type c2 byte auto insert mode enable transmit ais-p enable r/w r/w r/w r/w r/w r/w r/w r/w 0 1 0 0 0 0 0 0 this step configures the transmit sonet poh processor bl ock to set the value of the rei-p bit-fields (within the outbound sts-1 spe) based upon the data that it receives via the ?txp oh_n? input port. in this mode, the transmit sonet poh processor block will accept t he value corresponding to the rei-p fields (via the ?txpoh_n input port?) and it will write this data into the ?outbound ? sts-1 spe data-stream. step 2 ? begin providing the values of the ?outbound? rei-p bit-fields to the ?txpoh_n? input port. the procedure for applying the rei-p bit-values to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the rei-p bit valu es into the outbound sts-1 spe data-stream if the user intends to externally insert the rei-p bits into the outbound sts-1 spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do the following. ? continuously sample the ?txpohenable_n? and the ?txpohenable_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. ? whenever the ?external circuit? samples both t he ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., where it waits for 28 periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit this ?wait state? and then place the very first bit of the ?outbound? rei-p bit-fields onto the ?txpoh _n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmi t sonet poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 269 2.2.8.3.4 transmission of path trace messages via the j1 byte the transmit sonet poh processor block permits the us er to transmit path trace messages to the remote pte via the j1 byte. the transmit sonet poh proces sor block permits the user to accomplish this by either of the following options. ? automatically set the j1 byte (withi n each outbound sts-1 spe) to ?0x00? ? set and control the outbound j1 byte via on-chip register ? set and control the outbound j1 byte via external input pin ? use the ?transmit path trace message? buffer the details and instructions for using eit her of these features are presented below. 2.2.8.3.4.1 automatically setting the j1 byte (within each outbound sts-1 spe) to ?0x00? the xrt94l33 permits the user to configure each of the four (4) transmit sonet poh processor blocks to automatically set the contents of the j1 byte (within each outbound st s-1 spe) to ?0x00?. the user can accomplish this by writing the value ?[ 0, 0]? into bits 1 and 0 (j1 type[1:0]) within the appropriate ?transmit sonet path ? transmit j1 control? register; as depicted below. transmit sonet path ? transmit j1 control? register (address = 0xn9bb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j1 message length[1:0] j1 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x 0 0 once the user executes this step, then the corresp onding transmit sonet poh processor block(s) will be configured to automatically set the j1 byte (w ithin each outbound sts-1 spe) to the value ?0x00?. 2.2.8.3.4.2 using the ?transmit path trace message? buffer the xrt94l33 contains a total of four (4) ?transmi t path trace message buffers (one for each ?transmit sonet poh processor block, within the device). the address location of the ?transmit path trace messag e? buffer, for each of the four transmit sonet poh processor blocks is presented below. table 15: address locations of the transmit path trace message buffers within the xrt94l33 t ransmit sonet poh p rocessor b lock - c hannel a ddress l ocation of the t ransmit p ath t race m essage b uffer 0 0x1d00 ? 0x1d3f 1 0x2d00 ? 0x2d3f 2 0x3d00 ? 0x3d3f 3 0x4d00 ? 0x4d3f if the user wishes to use the ?path trace message? buffe r as the means to load and transmit the ?path trace message? to the remote pte, then the following steps must be executed.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 270 step 1 ? write the contents of this outbound ?path trace message? into the ?transmit path trace message? buffer. as the user writes the contents of the ?outbound? pa th trace message? into the ?transmit path trace? message buffer they must make sure that the first by te of the message is written into address location 0xnc00 (e.g., the very first address location of the ?transmit path trace message? buffer). step 2 ? specify the length of this ?path trace message? by writing the appropriate value into bits 3 and 2 (j1 message length[1:0]) within the ?transmit sonet path ? transmit j1 control? register; as depicted below. transmit sonet path ? transmit j1 control? register (address = 0xn9bb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j1 message length[1:0] j1 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x x x the relationship between the contents of ?j1_mess age_length[1:0]? and the corresponding length of the ?path trace message? is presented below in table _. table 16 the relationship between the contents of ?j1_message_length[1:0]? and the corresponding ?path trace message? length j1_m essage _l ength [1:0] p ath t race m essage l ength ( bytes ) 00 1 01 16 10 64 11 64 step 3 ? write the value ?[0, 1]? into bits 1 and 0 (j1_type[1:0]) within the transmit sonet path ? transmit j1 control register; as depicted below. transmit sonet path ? transmit j1 control? register (address = 0xn9bb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j1 message length[1:0] j1 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x 0 1 this step configures the transmit sonet poh processo r block to use the contents of the ?transmit path trace message? buffer as the source of the j1 byte, within each ?outbound? sts-1 spe.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 271 2.2.8.3.4.3 setting and controlling the ?out bound? j1 byte via on-chip register the transmit sonet poh processor bloc k permits the user to specify the co ntents of the j1 byte within the ?outbound? sts-1 spe, via software command. the user can configure the transmit sonet poh processor block to support this feat ure by performing the following steps. step 1 ? write the value ?[1, 0]? into bits 1 and 0 (j1 type[1:0]) within the ?transmit sonet path ? transmit j1 control? register, as depicted below. transmit sonet path ? transmit j1 control? register (address = 0xn9bb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j1 message length[1:0] j1 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x 1 0 this step configures the ?transmit sonet poh processo r? block to read out the contents of the ?transmit path ? transmit j1 byte value? register; and load this value into the ?j1 byte-field? within each outbound sts- 1 spe. step 2 ? write the desired byte value (for the ?outbound? j1 byte) into the ?transmit sonet path ? transmit j1 byte value? register. the bit-format of this register is presented below. transmit sonet path ? transmitter j1 value register (address = 0xn993) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_j1_byte[7:0] r/w r/w r/w r/w r/w r/w r/w r/w x x x x x x x x 2.2.8.3.4.4 setting and controlling the ?out bound? j1 byte via external input pin the transmit sonet poh processor bl ock permits the user to source th e contents of the j1 byte via the ?txpoh_n? input port. the user can configure the tr ansmit sonet poh processor block to support this feature by performing the following steps. step 1 ? write the value ?[1, 1]? into bits 1 and 0 (j1 type[1:0]) within the ?transmit sonet path ? transmit j1 control? register; as depicted below. transmit sonet path ? transmit j1 control? register (address = 0xn9bb) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j1 message length[1:0] j1 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 1 1 this step configures the ?transmit sonet poh processor? block to accept the value of the j1 byte, via the ?txpoh_n? input port and load this value into the j1 byte position within each outbound sts-1 spe.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 272 step 2 ? begin providing the values of the ?outbound? j1 byte message to the ?txpoh_n? input port. the procedure for applying the j1 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the j1 byte value into the outbound sts-1 spe data-stream if the user intends to externally in sert the j1 byte into the outbound sts-1 spe, via t he ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 49. figure 49: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in figure 49) is ?dashed? because cont rolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should place the very first bit (e.g., the mo st significant bit) of the ?outbound? j1 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sonet poh processor? bloc k circuitry, upon the very next rising edge of ?txpohclk_n?. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the j1 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 273 2.2.8.3.5 support/handling of the c2 byte the transmit sonet poh processor block permits the user to control the value of t he c2 byte by either of the following options. ? setting and controlling the ?outbound? c2 byte via software ? setting and controlling the ?outbound? c2 byte via the ?txpoh input port? the details and instructions for using eit her or these features are presented below. 2.2.8.3.5.1 setting and controlling the outbound c2 byte via software the transmit sonet poh processor block permits the user to specify the contents of the c2 byte, within the ?outbound? sts-1 spe via software command. the user can configure the transmit sonet poh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?0? into bit 2 (c2 insertion type) within the ?transmit sonet path ? sonet control register ? byte 0?, as depicted below. transmit sonet path ? sonet control register ? byte 0 (address = 0xn983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 0 0 0 0 0 0 0 0 this step configures the transmit sonet poh processo r block to read out the contents of the ?transmit sonet path ? transmit c2 byte value? register; and lo ad this value into the c2 byte position within each ?outbound? sts-1 spe. step 2 ? write the desired byte value (for the outbound c2 byte) into the ?transmit sonet path ? transmit c2 byte value? register. transmit sonet path ? transmit c2 byte value register (address = 0xn99f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_c2_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 274 2.2.8.3.5.2 setting and controlling the outboun d c2 byte via the ?txpoh_n input port? the transmit sonet poh processor block permits the user to specify the contents of the c2 byte, within the ?outbound? sts-1 spe, via data applied to the ?txpoh_n? input pin. the user can configure the transmit sonet poh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 2 (c2 byte insertion type) within the ?transmit sonet path ? sonet control register ? byte 0?, as depicted below. transmit sonet path ? sonet control register ? byte 0 (address = 0xn983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 0 0 0 0 0 1 0 0 this step configures the transmit sonet poh proces sor block to use the ?txpoh_n? input port as the source for the c2 byte, within each ?outbound? st s-1 spe. in this mode, the transmit sonet poh processor block will accept the value, corresponding to the c2 byte (via the ?txpoh_n? input port) and it will write this data into the c2 byte pos ition, within the ?outbound? sts-1 spe. step 2 ? begin providing the values of the ?outbound? c2 byte to the ?txpoh_n? input port. the procedure for applying the c2 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the c2 byte value into the outbound sts-1 spe data-stream if the user intends to externally insert the c2 byte into the outbo und sts-1 spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 275 figure 50.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 276 figure 50: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 277 figure 50) is ?dashed? because controlling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., wher e it will wait for 16 periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit th is ?wait state? and then place the very first bit (e.g., the most significant bit) of the ? outbound? c2 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sonet poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the c2 byte is the third byte within the poh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the c2 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. figure 51 presents an illustration of the ?txpoh input interface? waveforms, when the ?external circuit? is writing the c2 byte into the ?txpoh input port?. figure 51 illustration of the ?txpoh i nput interface? waveforms, when th e ?external circuit? is writing the ?c2 byte? into the ?txpoh input port?. 2.2.8.3.6 support/handling of the f2 byte the transmit sonet poh processor block permits the user to control the value of t he f2 byte by either of the following options. ? setting and controlling the ?outbound? f2 byte via software ? setting and controlling the ?outbound? f2 byte via the ?txpoh input port? the details and instructions for using eit her or these features are presented below. 2.2.8.3.6.1 setting and controlling the outbound f2 byte via software the transmit sonet poh processor block permits the user to specify the contents of the f2 byte, within the ?outbound? sts-1 spe via software command. the user can configure the transmit sonet poh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?0? into bit 7 (f2 insertion type) within the ?transmit sonet path ? sonet control register ? byte 0?, as depicted below. transmit sonet path ? sonet control register ? byte 0 (address = 0xn983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 0 0 0 0 0 0 0 0 this step configures the transmit sonet poh processo r block to read out the contents of the ?transmit sonet path ? transmit f2 byte value? register; and load this value into the f2 byte position within each ?outbound? sts-1 spe. step 2 ? write the desired byte value (for the outbound f2 byte) into the ?transmit sonet path ? transmit f2 byte value? register. the bit-format of this register is presented below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 278 transmit sonet path ? transmit f2 byte value register (address = 0xn9a3) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_f2_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.8.3.6.2 setting and controlling the outboun d f2 byte via the ?txpoh_n input port? the transmit sonet poh processor block permits the user to specify the contents of the f2 byte, within the ?outbound? sts-1 spe, via data applied to the ?txpoh_n? input pin. the user can configure the transmit sonet poh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 7 (f2 byte insertion type) within the ?transmit sonet path ? sonet control register ? byte 0?, as depicted below. transmit sonet path ? sonet control register ? byte 0 (address = 0xn983) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 f2 insertion type rei-p insertion type[1:0] rdi-p insertion type[1:0] c2 byte insertion type unused transmit ais-p enable r/w r/w r/w r/w r/w r/w r/o r/w 1 0 0 0 0 0 0 0 this step configures the transmit sonet poh proces sor block to use the ?txpoh_n? input port as the source for the f2 byte, within each ?outbound? st s-1 spe. in this mode, the transmit sonet poh processor block will accept the value, corresponding to the f2 byte (via the ?txpoh_n? input port) and it will write this data into the f2 byte pos ition, within the ?outbound? sts-1 spe. step 2 ? begin providing the values of the ?outbound? f2 byte to the ?txpoh_n? input port. the procedure for applying the f2 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the f2 byte value into the outbound sts-1 spe data-stream if the user intends to externally in sert the f2 byte into the outbound st s-1 spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 52. figure 52: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port?
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 279 txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in figure 52) is ?dashed? because cont rolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., wher e it will wait for 32 periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit th is ?wait state? and then place the very first bit (e.g., the most significant bit) of the ?outbound? f2 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sonet poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the f2 byte is the fifth byte within the poh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the f2 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. 2.2.8.3.7 support/handling of the h4 byte the transmit sonet poh processor block permits the user to control the value of t he h4 byte by either of the following options. ? setting and controlling the ?outbound? h4 byte via software ? setting and controlling the ?outbound? h4 byte via the ?txpoh input port? the details and instructions for using eit her or these features are presented below. 2.2.8.3.7.1 setting and controlling the outbound h4 byte via software the transmit sonet poh processor block permits the user to specify the contents of the h4 byte, within the ?outbound? sts-1 spe via software command. the user can configure the transmit sonet poh proc essor block to accomplish this by performing the following steps.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 280 step 1 ? write the value ?0? into bit 0 (h4 insertion type) within the ?transmit sonet path ? sonet control register ? byte 1?, as depicted below. transmit sonet path ? sonet control register ? byte 1 (address = 0xn982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 0 this step configures the transmit sonet poh processo r block to read out the contents of the ?transmit sonet path ? transmit h4 byte value? register; and lo ad this value into the c2 byte position within each ?outbound? sts-1 spe. step 2 ? write the desired byte value (for the outbound h4 byte) into the ?transmit sonet path ? transmit h4 byte value? register. the bit-format of this register is presented below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 281 transmit sonet path ? transmit h4 byte value register (address = 0xn9a7) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_h4_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.8.3.7.2 setting and controlling the outboun d h4 byte via the ?txpoh_n input port? the transmit sonet poh processor block permits the user to specify the contents of the h4 byte, within the ?outbound? sts-1 spe, via data applied to the ?txpoh_n? input pin. the user can configure the transmit sonet poh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 0 (f2 byte insertion type) within the ?transmit sonet path ? sonet control register ? byte 1?, as depicted below. transmit sonet path ? sonet control register ? byte 1 (address = 0xn982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 1 this step configures the transmit sonet poh proces sor block to use the ?txpoh_n? input port as the source for the h4 byte, within each ?outbound? st s-1 spe. in this mode, the transmit sonet poh processor block will accept the value, corresponding to the h4 byte (via the ?txpoh_n? input port) and it will write this data into the h4 byte pos ition, within the ?outbound? sts-1 spe. step 2 ? begin providing the values of the ?outbound? h4 byte to the ?txpoh_n? input port. the procedure for applying the h4 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the h4 byte value into the outbound sts-1 spe data-stream if the user intends to externally insert the h4 byte into the outbo und sts-1 spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 282 figure 53.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 283 figure 53: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 284 figure 53) is ?dashed? because controlling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., wher e it will wait for 40 periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit th is ?wait state? and then place the very first bit (e.g., the most significant bit) of the ? outbound? h4 byte onto the ?txpoh_n ? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sonet poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the h4 byte is the sixth byte within the poh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the h4 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. 2.2.8.3.8 support/handling of the z3 byte the transmit sonet poh processor block permits the user to control the value of t he h4 byte by either of the following options. ? setting and controlling the ?outbound? z3 byte via software ? setting and controlling the ?outbound? z3 byte via the ?txpoh input port? the details and instructions for using eit her or these features are presented below. 2.2.8.3.8.1 setting and controlling the outbound z3 byte via software the transmit sonet poh processor block permits the user to specify the contents of the z3 byte, within the ?outbound? sts-1 spe via software command. the user can configure the transmit sonet poh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?0? into bit 1 (z3 insertion type) within the ?transmit sonet path ? sonet control register ? byte 1?, as depicted below. transmit sonet path ? sonet control register ? byte 1 (address = 0xn982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 0 this step configures the transmit sonet poh processo r block to read out the contents of the ?transmit sonet path ? transmit z3 byte value? register; and load this value into the z3 byte position within each ?outbound? sts-1 spe. step 2 ? write the desired byte value (for the outbound z3 byte) into the ?transmit sonet path ? transmit z3 byte value? register. the bit-format of this register is presented below. transmit sonet path ? transmit z3 byte value register (address = 0xn9ab) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_z3_byte_value[7:0]
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 285 r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.8.3.8.2 setting and controlling the outboun d z3 byte via the ?txpoh_n input port? the transmit sonet poh processor block permits the user to specify the contents of the z3 byte, within the ?outbound? sts-1 spe, via data applied to the ?txpoh_n? input pin. the user can configure the transmit sonet poh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 1 (z3 byte insertion type) within the ?transmit sonet path ? sonet control register ? byte 1?, as depicted below. transmit sonet path ? sonet control register ? byte 1 (address = 0xn982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 1 0 this step configures the transmit sonet poh proces sor block to use the ?txpoh_n? input port as the source for the z3 byte, within each ?outbound? st s-1 spe. in this mode, the transmit sonet poh processor block will accept the value, corresponding to the z3 byte (via the ?txpoh_n? input port) and it will write this data into the z3 byte pos ition, within the ?outbound? sts-1 spe.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 286 step 2 ? begin providing the values of the ?outbound? z3 byte to the ?txpoh_n? input port. the procedure for applying the z3 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the z3 byte value into the outbound sts-1 spe data-stream if the user intends to externally in sert the z3 byte into the outbound st s-1 spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 54. figure 54 : a simple illustration of the ?external ci rcuit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (infigure 54) is ?dashed? because cont rolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., wher e it will wait for 48 periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit th is ?wait state? and then place the very first bit (e.g., the most significant bit) of the ?outbound? z3 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sonet poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the z3 byte is the seventh byte within the poh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the z3 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 287 2.2.8.3.9 support/handling of the z4 byte the transmit sonet poh processor block permits the user to control the value of t he z4 byte by either of the following options. ? setting and controlling the ?outbound? z4 byte via software ? setting and controlling the ?outbound? z4 byte via the ?txpoh input port? the details and instructions for using eit her or these features are presented below. 2.2.8.3.9.1 setting and controlling the outbound z4 byte via software the transmit sonet poh processor block permits the user to specify the contents of the z4 byte, within the ?outbound? sts-1 spe via software command. the user can configure the transmit sonet poh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?0? into bit 0 (z4 insertion type) within the ?transmit sonet path ? sonet control register ? byte 1?, as depicted below. transmit sonet path ? sonet control register ? byte 1 (address = 0xn982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 0 this step configures the transmit sonet poh processo r block to read out the contents of the ?transmit sonet path ? transmit z4 byte value? register; and load this value into the z4 byte position within each ?outbound? sts-1 spe. step 2 ? write the desired byte value (for the outbound h4 byte) into the ?transmit sonet path ? transmit z4 byte value? register. the bit-format of this register is presented below. transmit sonet path ? transmit z4 byte value register (address = 0xn9af) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_z4_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 288 2.2.8.3.9.2 setting and controlling the outboun d z4 byte via the ?txpoh_n input port? the transmit sonet poh processor block permits the user to specify the contents of the z4 byte, within the ?outbound? sts-1 spe, via data applied to the ?txpoh_n? input pin. the user can configure the transmit sonet poh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 0 (z4 byte insertion type) within the ?transmit sonet path ? sonet control register ? byte 1?, as depicted below. transmit sonet path ? sonet control register ? byte 1 (address = 0xn982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 1 0 0 this step configures the transmit sonet poh proces sor block to use the ?txpoh_n? input port as the source for the z4 byte, within each ?outbound? st s-1 spe. in this mode, the transmit sonet poh processor block will accept the value, corresponding to the z4 byte (via the ?txpoh_n? input port) and it will write this data into the z4 byte pos ition, within the ?outbound? sts-1 spe. step 2 ? begin providing the values of the ?outbound? z4 byte to the ?txpoh_n? input port. the procedure for applying the z4 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the z4 byte value into the outbound sts-1 spe data-stream if the user intends to externally in sert the z4 byte into the outbound st s-1 spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 55.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 289 figure 55: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (infigure 55) is ?dashed? because cont rolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., where it will wait for _ periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit this ?wait state? and then place the very first bit (e.g., the most significant bit) of the ?outbound? z4 byte onto the ?t xpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sonet poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because t he z4 byte is the 8th byte within the poh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the h4 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. 2.2.8.3.10 support/handling of the z5 byte the transmit sonet poh processor block permits the user to control the value of t he h4 byte by either of the following options. ? setting and controlling the ?outbound? z5 byte via software ? setting and controlling the ?outbound? z5 byte via the ?txpoh input port? the details and instructions for using eit her or these features are presented below. 2.2.8.3.10.1 setting and controlling the outbound z5 byte via software the transmit sonet poh processor block permits the user to specify the contents of the z5 byte, within the ?outbound? sts-1 spe via software command.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 290 the user can configure the transmit sonet poh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?0? into bit 0 (z5 insertion type) within the ?transmit sonet path ? sonet control register ? byte 1?, as depicted below. transmit sonet path ? sonet control register ? byte 1 (address = 0xn982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 x this step configures the transmit sonet poh processo r block to read out the contents of the ?transmit sonet path ? transmit z5 byte value? register; and load this value into the z5 byte position within each ?outbound? sts-1 spe. step 2 ? write the desired byte value (for the outbound z5 byte) into the ?transmit sonet path ? transmit z5 byte value? register. the bit-format of this register is presented below. transmit sonet path ? transmit z5 byte value register (address = 0xn9b3) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_z5_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.8.3.10.2 setting and controlling the outboun d z5 byte via the ?txpoh_n input port? the transmit sonet poh processor block permits the user to specify the contents of the z5 byte, within the ?outbound? sts-1 spe, via data applied to the ?txpoh_n? input pin. the user can configure the transmit sonet poh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 0 (z5 byte insertion type) within the ?transmit sonet path ? sonet control register ? byte 1?, as depicted below. transmit sonet path ? sonet control register ? byte 1 (address = 0xn982) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused z5 insertion type z4 insertion type z3 insertion type h4 insertion type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 1 0 0 0 this step configures the transmit sonet poh proces sor block to use the ?txpoh_n? input port as the source for the z5 byte, within each ?outbound? st s-1 spe. in this mode, the transmit sonet poh processor block will accept the value, corresponding to the z5 byte (via the ?txpoh_n? input port) and it will write this data into the z5 byte pos ition, within the ?outbound? sts-1 spe.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 291 step 2 ? begin providing the values of the ?outbound? z5 byte to the ?txpoh_n? input port. the procedure for applying the z5 byte to the ?txpoh_n? input port is presented below. using the ?txpoh? i nput port to insert the z5 byte value into the outbound sts-1 spe data-stream if the user intends to externally in sert the z5 byte into the outbound st s-1 spe, via the ?txpoh_n? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 56. figure 56: a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt95l34 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in figure 56) is ?dashed? because cont rolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txpohenable_n? and ?txpohframe_n? output pins ?high?, then it should enter a ?wait state? (e.g., where it will wait for _ periods of ?txpohclk_n? to elapse). afterwards, the external circuit should exit this ?wait state? and then place the very first bit (e.g., the most significant bit) of the ?outbound? z5 byte onto the ?t xpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sonet poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the z5 byte is the ninth byte within the poh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the z5 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 292 2.2.8.3.11 pointer-adjustment/ndf options forcing pointer adjustments and ndf events via software the ?transmit sonet poh processor? block permits the user to insert pointer adjustments or ndf events into the ?outbound? sts-1 data stream . specifically, the transmit sone t poh processor block permits the user to implement the following ?pointer-related? features. ? to force the pointer to shift to an ?arbitrary value? ? to configure the transmit sonet poh processor block to only insert poi nter-adjustment or ndf events, if no pointer-adjustment (ndf or otherwise) events have occurred within the last three (3) sts-1 framing periods. ? to force a ?positive-stuff? pointer-adjustment event ? to force a ?negative-stu ff? pointer-adjustment event ? to force a single ndf event ? to force a continuous ndf event ? to read out and determine the current ?pointe r-value? within the outbound sts-1 data-stream. the procedure for implementing each of these ?pointer-related? events is presented below. 2.2.8.3.11.1 forcing the pointer to shift to an arbitrary value the transmit sonet poh processor block permits the user to assign the arbitrary value to the pointer bytes, within the outbound sts-1 spe data-stream. the user c an invoke this feature by executing the following steps. step 1 ? write the appropriate ?ndf?, ?ss? and h1, h2 pointer values into the ?transmit sonet path ? transmit arbitrary h1 pointer? register, and the ?transmit sonet path ? transmit arbitrary h2 pointer? register. the bit-format for these two registers is presented below. transmit sonet path ? transmit arbitrary h1 byte pointer register (address = 0xn9bf) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 ndf bits ss bits h1 pointer value r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 transmit sonet path ? transmit arbitrary h2 byte pointer register (address = 0xn9c3) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 h2 pointer value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 293 step 2 ? induce a ?0 to 1 transition? in bit 5 (pointer force) within the ?transmit sonet path ? transmit path control register, as depicted below. transmit sonet path ? transmit path control register (address = 0xn9b7) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused pointer force check stuff insert negative stuff insert positive stuff insert continuous ndf events insert single ndf event r/o r/o r/w r/w w w r/w r/w 0 0 0 ->1 0 0 0 0 0 once the user induces this ?0 to 1 transition? in bit 5, then the following events will occur, within the very next ?outbound? sts-1 frame. ? the ndf bits, within the h1 byte, will be set to the va lue written into bits 4 through 7 (ndf bits) within the ?transmit sonet path ? transmit ar bitrary h1 byte pointer register. ? the ?ss? bits, within the h1 byte, will be set to t he value written into bits 2 and 3 (ss bits) within the ?transmit sonet path ? transmit ar bitrary h1 byte pointer register. ? the 10-bit pointer value (within bits 7 and 8, within the h1 byte, and all eight bits within the h2) will be set to the values written into bits 1 and 0 (h1 pointer) within the ?transmit sonet path ? transmit arbitrary h1 byte pointer? register, and bits 7 through 0 (h2 pointe r value) within the ?transmit sonet path ? transmit arbitrary h2 byte pointer? register. 2.2.8.3.11.2 forcing positive-stuff poin ter adjustment events via software the transmit sonet poh processor block permits the user to insert a ?positive-stuff? pointer adjustment event into the outbound sts-1 data-stream. this can be ac complished by inducing a ?0 to 1? transition in bit 2 (insert positive stuff) within the ?transmit sonet path ? transmit path control? register, as depicted below. transmit sonet path ? transmit path control register (address = 0xn9b7) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused pointer force check stuff insert negative stuff insert positive stuff insert continuous ndf events insert single ndf event r/o r/o r/w r/w w w r/w r/w 0 0 0 0 0 0 -> 1 0 0 once the user induces this ?0 to 1 transition? in bit 2, then the following events will occur. ? a ?positive-stuff? will occur (e.g., a single stuff byte will be inserted into the sts-1 data-stream, immediately after the h3 byte position). ? the ?i? bits, within the h1 and h2 bytes will be inve rted (to denote an ?incrementing? pointer adjustment) event. ? after the ?positive-stuff? event, t he pointer (consisting of the h1 and h2 bytes) will be incremented by ?1? and will be used as the new pointer from this point on. note: the contents of bit 2 (insert positive stuff) will be automatically cleared after the user has written a ?1? into this bit-field. hence, there is no need for the user to go back and write a ?0? into this bit-field.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 294 2.2.8.3.11.3 forcing negative-stuff poin ter adjustment events via software the transmit sonet poh processor bl ock permits the user to insert a ?positive-stuff? pointer adjustment event into the outbound sts-1 data-stream. this can be accomplished by inducing a ?0 to 1 transition? within bit 3 (insert negative stuff) within the ?transmit sonet path ? transmit path control? register; as depicted below. transmit sonet path ? transmit path control register (address = 0xn9b7) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused pointer force check stuff insert negative stuff insert positive stuff insert continuous ndf events insert single ndf event r/o r/o r/w r/w w w r/w r/w 0 0 0 0 0 ->1 0 0 0 once the user induces a ?0 to 1? transition in bit 3, then the following events will occur. ? a ?negative-stuff? will occur (e.g., a single payload byte will be inserted into the ?h3 byte? position, within the outbound sts-1 data-stream). ? the ?d? bits, within the h1 and h2 bytes will be inverted (to denote a ?decrementing? pointer-adjustment event). ? the contents of the h1 and h2 bytes will be decrem ented by ?1? and will be used as the new pointer from this point on. note: the contents of bit 3 (insert negative stu ff) will be automatically cleared after the user has written a ?1? into this bit-field. hence, there is no need for the user to go back and write a ?0? into this bit-field. 2.2.8.3.11.4 forcing a singl e ndf event via software the transmit sonet poh processor block permits the user to force a single ndf event into the outbound sts-1 data-stream. this can be accomplis hed by executing the following steps. step 1- write the new ?desired? pointer value into bits 1 and 0 (h1 pointer value) within the ?transmit sonet path ? transmit arbitrary h1 po inter register; and bits 7 through 0 (h2 pointer value) within the ?transmit sonet path ? tr ansmit arbitrary h2 pointer register. the bit-format of these two registers (with the relevant bit-fields shaded) is presented below. transmit sonet path ? transmit arbitrary h1 byte pointer register (address = 0xn9bf) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 ndf bits ss bits h1 pointer value r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 transmit sonet path ? transmit arbitrary h2 byte pointer register (address = 0xn9c3) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 h2 pointer value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 295 step 2 ? induce a ?0 to 1 transition? in bit 0 (i nsert single ndf event) within the ?transmit sonet path ? transmit path control? register; as depicted below. transmit sonet path ? transmit path control register (address = 0xn9b7) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused pointer force check stuff insert negative stuff insert positive stuff insert continuous ndf events insert single ndf event r/o r/o r/w r/w w w r/w r/w 0 0 0 0 0 0 0 0->1 once the user induces this ?0 to 1 transition? in bit 0, then the following events will occur. ? the ?n? bits, in the h1 byte (within the very nex t outbound sts-1 frame) will be set to the value ?1001?. ? the ten pointer value bits (within the h1 and h2 bytes) will be set to the value that was written into the ?transmit sonet path ? transmit arbitrary h1 byte po inter? and ?transmit sonet path ? transmit arbitrary h2 byte pointer? registers; during step 1.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 296 2.2.9 transmit sts-3 toh processor block the purpose of the transmit sts-3 toh processor block is to accomplish the following. ? to accept sts-3c spe data from the transmit sts- 3c poh processor block (for sts-3c applications) ? to accept 3 channels of sts-1 spe data from each of the three (3) transmit sonet poh processor blocks (for sts-3 applications) ? to compute and insert the b1 (secti on bip-8) and b2 (line bip-8) bytes. ? to source the k1/k2, e1, m0, j0, f1 and s1 bytes. ? to transmit the rdi-l (line ? re mote defect indicator) indicator. ? to transmit the rei-l (line ? remote error indicator) indicator. ? to transmit the ais-l (line ? alarm indication signal) indicator ? to deliberately transmit an erred b1 or b2 byte (for testing purposes) ? to optionally scramble the outbound sts-3 data. ? to output this data to either the transmit pecl inte rface or the transmit sts-3 telecom bus interface, for transmission to the remote terminal equipment. figure 57 presents an illustration of the functional bl ock diagram of the xrt9 4l33 atm uni/ppp/mapper ic with the transmit sts-3 toh processor block highlighted. figure 57: illustration of the functional block diag ram of the xrt94l33 atm uni/ppp/mapper ic with the transmit sts-3 toh processor block highlighted transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3/12 toh processor block receive sts-3/12 toh processor block transmit sts-3/12 toh processor block transmit sts-3/12 toh processor block receive sts-3/12 poh processor block receive sts-3/12 poh processor block transmit sts-3/12 poh processor block transmit sts-3/12 poh processor block sts-3/12 telecom bus interface block sts-3/12 telecom bus interface block sts-3/12 pecl interface block sts-3/12 pecl interface block sts-3/12 cdr block sts-3/12 cdr block xrt95l34 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block some background information on the transport overhead (toh) bytes as mentioned earlier, the xrt94l33 will handle either sts-1 frame, sts-3c frames, or sts-3. the size of an sts-3 frame is 9 rows by 270 byte columns. figure 58 presents a simple illustration of the sts-3 frame.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 297 figure 58: simple illustration of the sts-3 frame in the case of an sts-n frame, the first ?n x 3? column are referred to as the ?tr ansport overhead? (toh). therefore, in all, the toh consists of a total of 27 x n bytes. each of these poh bytes is briefly described below. a1, a2 ? framing alignment bytes j0 ? the section trace (growth) byte b1 ? the section bip-8 byte e1 ? the orderwire the operation of the ?transmit sts-3 toh processor? block is discussed in some detail below. 2.2.9.1 receiving sts-3 c spe data from the transmit sts-3 c poh processor block the transmit sts-3 toh processor block receives the sts-3c spe dat a (with newly derived poh bytes) from the transmit sts-3c poh processor block. as the transmit sts-3 toh processo r block receives the sts-3c spe dat a from the transmit sts-3c poh processor block, it will perfo rm the following functions. ? compute and insert the b1 byte ? compute and insert the b2 byte ? to source (per user configuration) the k1, k2, e1, m0, j0, f1 and s1 bytes. ? to (automatically or upon software command) transmit the rdi-l indicator ? to (automatically or upon software command) transmit the rei-l indicator ? to (upon software command) transmit the ais-l indicator ? to (optionally) scramble the data, prior to transm ission to the transmit pecl interface or the transmit sts-3 telecom bus interface blocks. each of these functions is described in considerable detail below. 2.2.9.2 computation and insertion of the section bip-8 (b1) byte the transmit sts-3 toh processor block computes a bip-8 value over an entire sts-3 frame. the results of this calculation are inserted into the b1 byte-position with in the very next sts-3 frame. the remote lte (line terminating equipment) w ill use this byte, in or der to perform error- checking/detection on the incoming st s-3 frames that it receives. transmission of erred b1 bytes in the outbound sts-3 data-stream the transmit sts-3 toh processor bloc k permits the user to insert errors into the b1 bytes, within the outbound sts-3 data-stream. the user can accomplish this by writing a ?non-zero? value into the ?transmit sts-3 transport ? transmit b1 byte error mask? register. the tr ansmit sts-3 toh proces sor block will perform an xor operation with the contents of ?outbound? b1 byte val ue and the contents of this register. the results of this calculation are loaded back into the b1 byte position, within the ?outbound? sts-3 data-stream.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 298 the bit-format of the ?transmit sts-3 transport ? trans mit b1 byte error mask? register is presented below. transmit sts-3 transport ? transmit b1 byte error mask register (address = 0x1923) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 b1_byte_error_mask[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 note: for normal (e.g., un-erred) operations, the user should ensu re that this register is set to ?0x00? (the default value). 2.2.9.3 computation and insertion of the line bip-8 (b2) byte the transmit sts-3 toh processor block also computes the bip-8 value over t he line overhead bytes, as well as the envelope capacity. the results of this calcul ation are inserted into the b2 byte-position within the very next sts-3 frame. the remote terminal equipment will use to this byte, in order to per form error- checking/detection in the incoming loh and envelope capacity data that it receives. transmission of erred b2 bytes in the outbound st s-3c data-stream the transmit sts-3 toh processor block permits the user to deliberately insert errors into the b2 bytes, within the outbound sts-3 data-stream. the user can accomplish this by writing a ?non-zero? value into the ?transmit sts-3 transport ? transmit b2 bit error mask? register. the trans mit sts-3 toh processor block will perform an xor oper ation with the contents of the ?outbound? b2 byte va lue and the contents of this register. the results of this calculation are loaded back into the b2 byte position(s), within the ?outbound? sts-3 data-stream. the bit-format of the ?transmit sts-3 transport ? trans mit b2 bit error mask? register is presented below. transmit sts-3 transport ? transmit b2 bi t error mask register (address = 0x192b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_b2_error_mask[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 note: for normal (e.g., un-erred) operations, the user should ensu re that this register is set to ?0x00? (the default value). 2.2.9.4 transmission of erred framing alignment bytes in the outbound sts-3 data-stream to be provided in the next revision of the data sheet.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 299 2.2.9.5 transmission of alarm conditions the transmit sts-3 toh processor bloc k supports the following functions. ? transmitting the los (loss of signal) pattern (under software control) ? transmitting the ais-l pattern (under software control) ? transmitting the rdi-l indicator ( automatically and under software control) ? transmitting the rei-l indicator ( automatically and under software control) each of these functions is discussed in some detail below. 2.2.9.5.1 transmission of the los condition the transmit sts-3 toh processor block permits the user to transmit the los pattern to the remote terminal equipment. the user can accomplish this by setting bit 3 (los force) within the transmit sts-3 transport ? sonet transmit control register ? byte 0, as illustrated below. transmit sts-3 transport ? sonet transmit control register ? byte 0 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 m0m1 insert method[0] unused rdi-l force ais-l force los force scramble enable b2 error insert a1a2 error insert r/w r/o r/w r/w r/w r/w r/w r/w 0 0 0 0 1 0 0 0 once the user executes this step, then the transmit sts-3 toh block will override a ll of the outbound data, with an ?all zeros? pattern. note: when this bit-field is set, it overrides all of the other bits in this register. 2.2.9.5.2 transmission of ais-l indicator the transmit sts-3 toh processor block permits the us er to transmit the ais-l (line ? alarm indication signal) indicator to the remote terminal equipment, under software control. forced transmission of the ais-l indicator the user can command the transmit sts-3 toh processo r block to transmit the ais-l indicator by setting bit 4 (ais-l force) within the transmit sts-3 transport ? sonet transmit control register ? byte 0, to ?1? as illustrated below. transmit sts-3 transport ? sonet transmit control register ? byte 0 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 m0m1 insert method[0] unused rdi-l force ais-l force los force scramble enable b2 error insert a1a2 error insert r/w r/o r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 0 once the user exec utes this step, then the transmit sts-3 toh processor block will over write all of the line overhead, and sts-3 envelope capacity bytes, with an ?all ones? pattern. only the section overhead bytes will be unaffected by this register bit setting. note: this bit-field is ignored when the ?l os force? bit-field is set to ?1?.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 300 2.2.9.5.3 transmission of the rdi-l indicator the transmit sts-3 toh processor block provides the us er with two options associated with transmitting the line-remote defect indicator (rdi-l). ? forced transmission of the rdi-l i ndicator (e.g., under software control). ? automatic transmission of the rdi-l indicator each of these options is discussed below. 2.2.9.5.3.1 forced transmission of the rdi- l indicator (under software control) the xrt94l33 permits the user to force the transmit sts-3 toh processor block to transmit the rdi-l indicator to the remote terminal equipment. the user can accomplish this by setting bit 5 (rdi-l force), within the transmit sts-3 transport ? sonet transmit c ontrol register ? byte 0, to ?1? as illustrated below. transmit sts-3 transport ? sonet transmit control register ? byte 0 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 m0m1 insert method[0] unused rdi-l force ais-l force los force scramble enable b2 error insert a1a2 error insert r/w r/o r/w r/w r/w r/w r/w r/w 0 0 1 0 0 0 0 0 if the user opts to transmit an rdi-l indicator, then bi ts 6, 7 and 8 (of the k2 byte, within each outbound sts- 3c frame) will be set to the value [1, 1, 0]. note: this bit-field is ignored when either the ?los force? or the ?ais-l force? bit-fields are set to ?1?. in this case, if the user wishes to terminate the tr ansmit sts-3c toh processor block?s transmission of the rdi-l indicator, then they only need to set bit 5 back to ?0?. 2.2.9.5.3.2 automatic transmission of th e rdi-l (line ? remote defect indicator) the transmit sts-3 toh processor bloc k permits the user to configure it to automatically transmit the rdi-l indicator, in response to the following conditions. ? the corresponding receive sts-3 toh processor bl ock declares an los (loss of signal) condition. ? the corresponding receive sts-3 toh processor block is declaring an lof (loss of frame) condition. ? the corresponding receive sts-3 toh processo r block is declaring the ais-l condition. bits 0 through 2, within the transmit sts-3 transport ? rdi-l control register, permits the user configure the transmit sts-3 toh processor block to support t he ?automatic transmission of an rdi-l indicator upon detection of these conditions. these bi t-fields are highlighted and defined below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 301 transmit sts-3 transport ? rdi-l control register (address = 0x1933) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused external rdi-l enable transmit rdi-l upon ais transmit rdi-l upon lof transmit rdi-l upon los r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 1 1 1 b it n umber n ame t ype d escription 2 transmit rdi-l upon ais r/w transmit line remote defect indicator (rdi-l) upon detection of ais-l: this read/write bit-field permits the user to configure the sts-3 transmitter to automatically transmit a rdi-l indicator to the remote terminal anytime (and for the duration) that the corresponding sts-3 receiver is detecting a line ais (ais-l) indicator. 0 ? configures the sts-3 transmi tter to not automatically transmit the rdi-l indicator, upon the corresponding sts-3 receiver detecting the ais-l indicator. 1 ? configures the sts-3 transmitter to automatically transmit the rdi-l indicator, upon the corresponding sts-3 receiver detecting the ais-l indicator. 1 transmit rdi-l upon lof r/w transmit line remote defect indicator (rdi-l) upon detection of lof: this read/write bit-field permits the user to configure the sts-3 transmitter to automatically transmit a rdi-l indicator to the remote terminal anytime (and for the duration) that the corresponding sts-3 receiver is declaring the lof defect. 0 ? configures the sts-3 transmi tter to not automatically transmit the rdi-l indicator, upon the corresponding sts-3 receiver declaring the lof defect. 1 ? configures the sts-3 transmitter to automatically transmit the rdi-l indicator, upon the corresponding sts-3 receiver declaring the lof defect. 0 transmit rdi-l upon los r/w transmit line remote defect indicator (rdi-l) upon detection of los: this read/write bit-field permits the user to configure the sts-3 transmitter to automatically transmit a rdi-l indicator to the remote terminal anytime (and for the duration) that the corresponding sts-3 receiver is declaring the los defect. 0 ? configures the sts-3 transmi tter to not automatically transmit the rdi-l indicator, upon the corresponding sts-3 receiver declaring the los defect. 1 ? configures the sts-3 transmitter to automatically transmit the rdi-l indicator, upon the corresponding sts-3 receiver declaring the los defect.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 302 how automatic transmission of the rdi-l indicator works consider that the transmit sts-3 toh processor bloc k (within a given channel) has been configured to automatically transmit the rdi-l i ndicator whenever the corresponding receive sts-3 toh processor block detects an los condition. figure 59 presents a simple illustration of the transmit sts-3 toh processor and receive sts-3 toh processor block pair. further, this figure indicates that the receive sts-3 toh processor block is not declaring the los condition. figure 59 illustration of a transmit sts-3 toh pr ocessor and receive sts-3 toh processor block pair, when los is not being declared. as a consequence, the transmit sts-3 toh processor bloc k will, in-turn, not transm it the rdi-l indicator (by setting bits 6, 7 and 8, of the k2 byte, to a value other than [1, 1, 0]). figure 57 presents a different illustration of the transmit sts-3 toh processor and receive sts-3 toh processor blocks. in this case, the receive sts-3 to h processor block is now declaring the los condition. as a consequence, the transmit sts-3 toh processor bloc k will, in-turn, transmit the rdi-l indicator, by setting bits 6, 7 and 8 (of the k2 byte), within the outbound sts-3 signal to the value [1, 1, 0]. figure 60 illustration of the transmit sts-3 toh pr ocessor block transmitting the rdi-l indicator to the remote terminal coincident with the rece ive sts-3 toh processor block declaring an los condition. 2.2.9.5.4 transmission of the rei-l indicator the transmit sts-3 toh processor block can be config ured to transmit the rei-l indicator either (1) automatically, (2) upon software command, or (3) via t he txpoh external input port, as described below. 2.2.9.5.4.1 configuring the transmit sts-3 toh processor block to automatically transmit the rei-l indicator the user can configure the transmit sts-3 toh processo r block to automatically transmit the rei-l indicator whenever the corresponding receive sts-3c toh proc essor block detects at least one b2 byte error. the user can configure the transmit sts-3 toh proc essor block to automatica lly transmit the rei-l indicator, in response to detection of b2 by te errors, by executing the following steps. step 1 ? write the value ?0? into bit 0 (m0m1 insert method[1]) within the ?transmit sts-3 transport ? sonet transmit control register ? byte 1?; as depicted below. transmit sts-3transport ? sonet transmit control register ? byte 1 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved e2 insert method e1 insert method f1 insert method s1 insert method k1k2 insert method m0m1 insert method[1] r/o r/o r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 303 step 2 ? write the value ?0? into bit 7 (m0m1 insert method[0]) within the ?transmit sts-3 transport ? sonet transmit control register ? byte 0?; as depicted below. transmit sts-3 transport ? sonet transmit control register ? byte 0 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 m0m1 insert method[0] unused rdi-l force ais-l force los force scramble enable b2 error insert a1a2 error insert r/w r/o r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 steps 1 and 2 configure the transmit sts-3 toh processor block to automatically set bits 5 through 8 (of the m0 byte) within the ?outbound? sts-3 data-stream , to the appropriate rei-l value based upon receive conditions as detected by the correspondi ng ?receive sts-3 toh processor? block. step 3 ? indicate whether or not the rei-l value (transmitted to the remote lte) reflects the number of bits (within the b2 byte) that are in error, or the number of erred sts-3 frames that have been detected by the corresponding receive sts-3 toh processor block. the xrt94l33 permits the user to (1) flag b2 byte errors , and (2) to transmit the resulting rei-l values (back to the remote lte) by the following means. ? by flagging and reporting the number of bits (within the b2 byte(s)) that have been determined to be in error, within a given sts-3 frame. ? by flagging and reporting whether or not the corr esponding receive sts-3 toh processor block is currently receiving an erred sts-3 frame. the user can choose between these two options by writ ing the appropriate value into bit 1 (b2 error type) within the ?receive sts-3 transport ? contro l register ? byte 0?, as depicted below. receive sts-3 transport control register ? byte 0 (address = 0x1103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused sf detect enable sd detect enable descramble disable sdh/sonet* rei-l error type b2 error type b1 error type r/o r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 x 0 setting this bit-field to ?0? configures the ?transmit sts-3 toh processor? block to set the rei-l bit-fields (within the m0 byte) of the ?outbound? sts-3 frame to a value that reflects the number of bits (within the b2 byte) that were determined to be in error (withi n the most recently received sts-3 frame) by the corresponding receive sts-3 toh processor block. in th is case, the rei-l bit-fields can range in value from ?0? (for no b2 byte errors) to ?8? (for all b2 bits being in error). setting this bit-field to ?1? configures the ?transmit sts-3 toh processor? block to set the rei-l bit-fields (within the m0 byte) of the ?outbound? sts-3 frame; to a value that indicates whether or not at least one b2 bit error was detected within the most recently receiv ed sts-3 frame; by the co rresponding receive sts-3 toh processor block. in this mode, t he transmit sts-3 toh processor block w ill set the ?rei-l? bit-fields (within the ?outbound? sts-3 frame) to ?0? if the correspond ing receive sts-3 toh processor block is not detecting any b2 byte errors, in its incoming sts-3 data-stream. conversely, the transmit sts-3 toh processor block will set the ?rei-l? bit-fields (within the ?outbound? sts-3 frame) to ?1? if the corresponding receive sts- 3 toh processor block receives an sts-3 frame that contains a b2 byte error.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 304 2.2.9.5.4.2 configuring the transmit sts-3 toh pr ocessor block to transmit the rei-l indicator, upon software command the user can configure the transmit sts-3 toh processo r block to transmit the rei-l indicator (per software command) by executing the following steps. step 1 ? write the value ?0? into bit 0 (m0m1 insert method[1]) within the ?transmit sts-3 transport ? sonet transmit control register ? byte 1? as depicted below. transmit sts-3transport ? sonet transmit control register ? byte 1 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved e2 insert method e1 insert method f1 insert method s1 insert method k1k2 insert method m0m1 insert method[1] r/o r/o r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 step 2 ? write the value ?1? into bit 7 (m0m1 insert method[0]) within the ?transmit sts-3 transport ? sonet transmit control register ? byte 0? as depicted below. transmit sts-3 transport ? sonet transmit control register ? byte 0 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 m0m1 insert method[0] unused rdi-l force ais-l force los force scramble enable b2 error insert a1a2 error insert r/w r/o r/w r/w r/w r/w r/w r/w 1 0 0 0 0 0 0 0 steps 1 and 2 configure the transmit sts-3 toh processor block to autom atically read out the contents of bit 0 through 3 (of the transmit sts-3 transport ? m0m1 byte value register) and write the value of these bits into bits 5 through 8 (of the m0m1 byte) within the ?outbound? sts-3 frame. the bit-format of the ?transmit sts-3 transport ? transmit m0m1 byte val ue? register (with the appropriate bits ?shaded?) is presented below. transmit sts-3 transport ? m0m1 value register (address = 0x1937) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_m0m1_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 in this mode, the user can transmit an ?un-erred? re i-l value by setting bits 0 through 3 (of the transmit sts-3 transport ? transmit m0m1 byte value register) to ?[0, 0, 0, 0]?. converse ly, the user can transmit an ?erred? rei-l value by setting bits 0 through 3 (within the transmit sts-3 transport ? transmit m0m1 byte value register) to some value between 1 and 8. a utomatic t ransmission of the rei-l i ndicator the transmit sts-3 toh processor bl ock will transmit the line ? remote error indicator to the remote terminal equipment. in an sts-3 frame, the rei-l indica tor will be transmitted within the m0 byte. the bit- format of the m0 byte is presented below in
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 305 figure 61.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 306 figure 61 bit format of the m0 byte b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 b it 8 undefined b2 erro r count (rei-l)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 307 figure 61 indicates that bits 5 through 8, within the m0 byte are allocated for the rei-l function. the purpose of the rei-l function, within the m0 is two-fold. 1. it permits a piece of line terminating equipment (lte), which is transmitting sts-3 data to a remote line terminating equipment, to determine whether or not the remote lte is receiving its line overhead and sts-3c envelope capacity bytes, in an error-free manner. 2. it permits an lte (which is receiving sts-3c data fr om a remote lte) to inform this remote terminal when it is receiving ?erred? line overhead and sts- 3 envelope capacity bytes; within the incoming sts-3 frames. the role of rei-l is best presented in the practical example below. example: consider a ?near-end? lte that is communicating with a remote lte. this ?near-end? lte consists of the receive sts-3 toh processor block and the transmit sts-3 toh processor block, within a given channel in the xrt94l33 atm uni/ppp/mapper ic; as depicted below in
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 308 figure 62 and figure 63. the ?transmit sts-3 toh processor? block will transmit sts-3 frames to the remote lte. likewise, the ?receive sts-3 toh processor? block will receive and process sts-3 frames, originating from the remote lte. the ?near-end? receive sts-3 toh processor? block is going to verify the values of the b2 bytes, within the incoming sts-3 frames (from the remote lt e). if the ?near-end? receive sts-3 toh processor? block detects no b2 byte errors, in th e incoming sts-3 frame, then it will not ify the remote lte of this fact, by having the ?near-end? transmit sts-3 toh processor? block set the ?rei-l? bits, within the m0 byte (in the ?outbound? sts-3 frame) to the value ?0?. this phenomenon is illustrated in
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 309 figure 62 and figure 63 below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 310 figure 62 illustrates the ?near-end? receive sts-3 to h processor block receiving an ?error-free? sts-3 frame. in this figure, the locally computed b2 value of ?0x5a? matches that received from the remote lte. figure 63 illustrates the s ubsequent action of the ?near -end? transmit sts-3 toh processor block, which will transmit an sts-3 frame, with the rei-l bit-fields (within the m0 byte) se t to ?0?; to the remote lte. this signaling indicates that the ?near-end? lte has received an error-free line overhead and sts-3 envelope capacity data in the most recently rece ived sts-3 frame, from the remote lte.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 311 figure 62 illustration of the ?near-end? receive st s-3 toh processor block receiving a sts-3 frame (from the remote lte) with the correct b2 byte value remote lte remote lte transmit sts-1 toh processor block transmit sts-1 toh processor block receive sts-1 toh processor block receive sts-1 toh processor block near-end lte locally computed b2 byte = 0x5a 0x5a b2 byte incoming sts-1 frame figure 63 illustration of the ?near-end? transmit sts-3 toh processor blo ck transmitting an sts-3 frame (to the remote lte) with the rei-l value set to ?0? remote lte remote lte transmit sts-1 toh processor block transmit sts-1 toh processor block receive sts-1 toh processor block receive sts-1 toh processor block near-end lte 0x00 m0 byte outbound sts-1 frame conversely, if the ?near-end? receive sts-3 toh proces sor block detects an error in the incoming b2 byte, then it will notify the remote lte of this fact, by having the ?near-end? transmit sts-3 toh processor block set the ?rei-l? bits, within the ?outbound? sts-3 frame (w hich is destined for the remote lte) to the value, reflecting the total number of bit-errors t hat have been detected within the b2 byte. figure 64 illustrates the ?n ear-end? receive sts-3 to h processor block receiving an erred sts-3 frame from the remote lte. in this figure, the ?near-end ? receive sts-3 toh processor block is receiving an sts-3 frame, with a b2 byte value of ?0x5f?. this va lue does not match the ?locally computed? b2 byte value of ?0x5a?. consequently, there is an error in the line overhead and sts-3c envelope capacity bytes, within this sts-3 frame. now, since this b2-byte mismatch is due to two bits being in error, the rei-l bits will be set to the value ?2?.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 312 figure 64 illustration of the ?near- end? receive sts-3 toh processor block receiving an sts-3 frame (from the remote lte) with an incorrect b2 byte remote lte remote lte transmit sts-1 toh processor block transmit sts-1 toh processor block receive sts-1 toh processor block receive sts-1 toh processor block near-end lte locally computed b2 byte = 0x5a 0x5f b2 byte incoming sts-1 frame figure 65 illustration of the ?near-end? transmit sts-3 toh processor block, transmitting an sts-3 frame (to the remote lte) with the rei-l bits being set to ?2? remote lte remote lte transmit sts-1 toh processor block transmit sts-1 toh processor block receive sts-1 toh processor block receive sts-1 toh processor block near-end lte 0x02 m0 byte outbound sts-1 frame for information on how the receive sts-3 toh processor block processes the rei-l bit-fields, within each incoming sts-3 frame, please see section _. 2.2.9.5.5 transmission of section trace messages via the j0 byte the transmit sts-3 toh processor block permits the user to transmit section trace messages to the remote lte via the j0 byte. the transmit sts-3 toh pr ocessor block permits the user to accomplish this by either of the following options.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 313 ? automatically set the j0 byte (within each outbound sts-3 frame) to ?0x01? ? set and control the outbound j0 byte via on-chip register ? set and control the outbound j0 byte via external input pin ? use the ?transmit section trace message? buffer the details and instructions for using eit her of these features are presented below. 2.2.9.5.5.1 automatically setti ng the j0 byte (within each outbound sts-3 frame) to ?0x01? the xrt94l33 permits the user to configure each of the four (4) transmit sts-3 toh processor blocks to automatically set the contents of the j0 byte (within each outbound sts-3 frame) to ?0x01?. the user can accomplish this by writing the value ?[ 0, 0]? into bits 1 and 0 (j0 type[1:0]) within the appropriate ?transmit sts-3 transport ? transmit j0 byte control? register; as depicted below. transmit sts-3 transport ? transmit j0 byte control register (address = 0x194f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j0 message length[1:0] j0 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x 0 0 once the user executes this step, then the corresp onding transmit sts-3 toh processor block(s) will be configured to automatically set the j0 byte (wit hin each outbound sts-3 frame) to the value ?0x01?. 2.2.9.5.5.2 transmitting 16-byte /64-byte section trace messages using the ?transmit section trace message? buffer the xrt94l33 contains a total of four (4) ?transmit section trace message? buffers (one for each ?transmit sts-3 poh processor block, within the device). th e address location of the ?transmit section trace message? buffer for each of the four transmit sts-3 toh processor blocks is presented below. table 17: address locations of the transmit section trace message buffers within the xrt94l33 t ransmit sts-3 toh p rocessor b lock - c hannel a ddress l ocation of the t ransmit s ection t race m essage b uffer 0 0x1b00 ? 0x1b3f 1 0x2b00 ? 0x2b3f 2 0x3b00 ? 0x3b3f 3 0x4b00 ? 0x4b3f if the user wishes to use the ?section trace message? buffer as the means to load and transmit the ?section trace message? to the remote ste, then they must execute t he following steps. step 1 ? write the contents of this outbound ?section trace message? into the ?transmit section trace message? buffer. as the user writes the contents of the ?outbound? sect ion trace message? into the ?transmit section trace? message buffer they must make sure that the first by te of the message is written into address location 0xnb00 (e.g., the very first address location of the ?transmit section trace message? buffer). step 2 ? specify the length of this ?section trace message? by writing the appropriate value into bits 3 and 2 (j0 message length[1:0]) within the ?trans mit sts-3 transport ? transmit j0 byte control? register; as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 314 transmit sts-3 transport ? transmit j0 byte control register (address = 0x194f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j0 message length[1:0] j0 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x x x the relationship between the contents of ?j0_mess age_length[1:0]? and the corresponding length of the ?section trace message? is presented below in table _. table 18: the relationship between the contents of the ?j0_message_length[1:0]? and the corresponding ?section trace message? length j0_m essage _l ength [1:0] s ection t race m essage l ength ( bytes ) 00 1 01 16 10 64 11 64 step 3 ? write the value ?[0, 1]? into bits 1 and 0 (j0_type[1:0]) within the transmit sts-3 transport ? transmit j0 control register; as depicted below. transmit sts-3 transport ? transmit j0 byte control register (address = 0x194f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j0 message length[1:0] j0 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x 0 1 this step configures the transmit sts-3 toh processor block to use the contents of the ?transmit section trace message? buffer as the source of the j0 byte, within each ?outbound? sts-3 frame. 2.2.9.5.5.3 setting and controlling the ?out bound? j0 byte via on-chip register the transmit sts-3 toh processor block permits the user to specify the contents of the j0 byte within the ?outbound? sts-3 frame, via software command. the us er can configure the transmit sts-3 toh processor block to support this feature by performing the following steps. step 1 ? write the value ?[1, 0]? into bits 1 and 0 (j0 type[1:0]) within the ?transmit sts-3 transport ? transmit j0 byte control? register, as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 315 transmit sts-3 transport ? transmit j0 byte control register (direct address = 0xn84f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j0 message length[1:0] j0 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x 1 0 this step configures the ?transmit sts-3 toh processo r? block to read out the contents of the ?transmit transport ? transmit j0 byte value? register; and load this value into the ?j0 byte-field? within each outbound sts-3 frame. step 2 ? write the desired byte value (for the ?outbound? j0 byte) into the ?transmit sts-3 transport ? transmit j0 byte value? register. the bit-format of this register is presented below. transmit sts-3 transport ? transmitter j0 value register (address = 0x194b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_j0_byte[7:0] r/w r/w r/w r/w r/w r/w r/w r/w x x x x x x x x 2.2.9.5.5.4 setting and controlling the ?out bound? j0 byte via external input pin the transmit sts-3 toh processor block permits the us er to source the contents of the j0 byte via the ?txtoh_n? input port. the user can configure the tr ansmit sts-3 toh processor block to support this feature by performing the following steps. step 1 ? write the value ?[1, 1]? into bits 1 and 0 (j0 type[1:0]) within the ?transmit sts-3 transport ? transmit j0 byte control? register; as depicted below. transmit sts-3 transport ? transmit j0 control register (address = 0x194f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused j0 message length[1:0] j0 type[1:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x 1 1 this step configures the ?transmit sts-3 toh processor? block to accept the value of the j0 byte, via the ?txtoh? input port and load this value into the j0 byte position within each outbound sts-3 frame. step 2 ? begin providing the values of the ?outbound? j0 byte message to the ?txtoh? input port. the procedure for applying the j0 byte to the ?txtoh? input port is presented below. using the ?txtoh? input port to insert the j0 byte value into the outbound sts-3 frame if the user intends to externally insert the j0 byte in to the outbound sts-3 frame, the ?txtoh? input port, then they must design some external circuitry (which can be realized in an asic, fpga or cpld solution) to do the following. ? continuously sample the ?txtohenable_n? and the ?txtohframe_n? output pins upon the rising edge of the ?txtohclk_n? output clock signal. a simple illustration of this ?external circuit? being inte rfaced to the ?txtoh input port? is presented below in figure 66.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 316 figure 66 a simple illustration of the ?external circ uit? being interfaced to the ?txtoh input port? note: the ?txtohins_n? line (in figure 66) is ?dashed? because c ontrolling this signal is not necessary if the user has executed ?step 1? above. ? whenever the ?external circuit? samples both the ?txtohenable_n? and the ?txtohframe_n? output pins ?high?, then it should enter a wait state (e.g., where it will wait for 16 periods of ?txtohclk_n? to elapse). afterwards, the external circuitry should exit this ?w ait state? and then place the very first byte (e.g., the most significant bit) of the ?outbou nd? j0 byte onto the ?txtoh_n? input pin, upon the very next falling edge of ?txtohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3 toh processor? block circuitry, upon the very next rising edge of ?txtohclk_n. note: this ?wait state? period is necessary because the j0 byte is the third byte within the toh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the j0 byte) onto the ?txtoh_n? input pin, upon each of the nex t seven falling edge of ?txtohclk_n?. ? the ?external circuit? should then revert back to c ontinuously sampling the stat es of the ?txtohenable_n? and ?txtohframe_n? output pins and repeat the above-mentioned process. figure 67 presents an illustration of the ?txtoh input interface? waveforms, when the ?external circuit? is writing the j0 byte into the ?txtoh input port?. figure 67 illustration of the ?txtoh i nput interface? waveforms, when th e ?external circuit? is writing the j0 byte into the ?txtoh input port? 2.2.9.5.6 support/handling of the e1 byte the transmit sts-3c toh processor bloc k permits the user to control the valu e of the e1 byte which is to be transmitted via the ?outbound? sts-3c data-s tream by either or the following options. ? setting and controlling the e1 byte via software ? setting and controlling the e1 byte via the ?txpoh input port? the details and instructions for using eit her of these features are presented below. 2.2.9.5.6.1 setting and controlling the outbound e1 byte via software the transmit sts-3c toh processor block permits the user to specify the contents of the e1 byte within the outbound sts-3c data-stream via software command. the user can configure the transmit sts-3c toh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 4 (e1 insert method) within the ?transmit sts-3c transport ? sonet transmit control register ? byte 1, as depicted below. transmit sts-3transport ? sonet transmit control register ? byte 1 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved e2 insert method e1 insert method f1 insert method s1 insert method k1k2 insert method m0m1 insert method[1] r/o r/o r/w r/w r/w r/w r/w r/w 0 0 x 1 x x x x the step configures the transmit sts-3c toh proces sor block to read out the contents of the ?transmit sts-3c transport ? e2 byte value register, and load this value into the e1 byte position within each outbound sts-3c data-stream.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 317 step 2 ? write the desired byte values (for the outbound e1 byte) into the ?transmit sts-3c transport ? e1 byte value register. the bit-format for this register is presented below. transmit sts-3 transport ? transmit e1 byte value register (address = 0x1943) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_e1_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.9.5.6.2 setting and controlling the outbo und e1 byte via ?txpoh input port? the transmit sts-3c toh processor block permits the user to specify the contents of the e1 byte within the ?outbound? sts-3c data-stream via the dat a applied to the ?txpoh_n? input port. the user can configure the transmit sts-3c toh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 4 (sts-3c toh in sert) within the ?mapper control register ? byte 2?, as depicted below. mapper control register ? byte 2 (direct address = 0xn601) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sts-3c oh pass thru sts-3c remote loop-back sts-3c local loop- back sts-3c toh insert loop-timing poh pass thru receive (ingress) sts-3c enable transmit (egress) sts-3c enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 0 this step enables the ?transmit sts-3c toh processor? block (associated with channel ?n?) to accept its toh bytes via the ?txpoh input? port.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 318 step 2 ? write the value ?0? into bit 4 (e1 insert method) within the ?transmit sts-3c transport ? sonet transmit control register ? byte 1; as depicted below. transmit sts-3transport ? sonet transmit control register ? byte 1 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved e2 insert method e1 insert method f1 insert method s1 insert method k1k2 insert method m0m1 insert method[1] r/o r/o r/w r/w r/w r/w r/w r/w 0 0 x 0 x x x x this step configures the transmit sts-3c toh processo r block to use the ?txpoh input? port as the source for the e1 byte, within each outbound sts-3c frame. in this mode, the transmit sts-3c toh processor block will accept the value, corresponding to the e1 byte (via the ?txpoh_n? input port) and it will write this data into the e1 byte position, within the ?outbound? sts-3c frame. using the ?txpoh_n input? port to insert the e1 byte value into the ?outbound? sts-3c data-stream if the user intends to externally insert the e1 byte into the outbound sts-3c data-stream, via the ?txpoh_n? input port, then they must design some external circuitr y (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 68. figure 68 a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt94l43 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in figure 68) is ?dashed? because this controlling this signal is not necessary if the user has executed ?step 2? above.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 319 ? whenever the ?external circuit? samples the ?txpohframe_n? output pin ?high? and also the ?txpohenable_n? pin ?low?, then it should enter a ?wait state? (e.g., where it waits for __ periods of ?txpohclk_n? to elapse). afterwards, the external ci rcuit should exit this ?wait state? and then place the very first bit (e.g., the most significant bit) of the ?outbound? e1 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because t he e1 byte is the _ byte within the toh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the e1 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. figure 69 presents an illustration of the ?txpoh input interface? waveforms, when the ?external circuit? is writing the e1 byte into the ?txpoh input port?. figure 69 illustration of the ?txpoh i nput interface? waveforms, when th e ?external circuit? is writing the ?e1 byte? into the ?txpoh input port? 2.2.9.5.7 support/handling of the f1 byte the transmit sts-3c toh processor block permits the user to control the value of the f1 byte, which is to be transmitted via the ?outbound? sts-3c data-s tream by either or the following options. ? setting and controlling the f1 byte via software ? setting and controlling the f1 byte via the ?txpoh input port? the details and instructions for using eit her of these features are presented below. 2.2.9.5.7.1 setting and controlling the outbound f1 byte via software the transmit sts-3c toh processor block permits the user to specify the contents of the e1 byte within the outbound sts-3c data-stream via software command. the user can configure the transmit sts-3c toh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 3 (f1 insert method) within the ?transmit sts-3c transport ? sonet transmit control register ? byte 1, as depicted below. transmit sts-3ctransport ? sonet transmit control register ? byte 1 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved e2 insert method e1 insert method f1 insert method s1 insert method k1k2 insert method m0m1 insert method[1] r/o r/o r/w r/w r/w r/w r/w r/w 0 0 x 0 1 x x x the step configures the transmit sts-3c toh proces sor block to read out the contents of the ?transmit sts-3c transport ? f1 byte value register, and load this value into the f1 byte position within each outbound sts-3c data-stream. step 2 ? write the desired byte values (for the outbound f1 byte) into the ?transmit sts-3c transport ? f1 byte value register. the bit-format for this register is presented below. transmit sts-3c transport ? transmit f1 byte value register (address = 0x1943)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 320 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_f1_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.9.5.7.2 setting and controlling the outbo und f1 byte via ?txpoh input port? the transmit sts-3c toh processor block permits the user to specify the contents of the e1 byte within the ?outbound? sts-3c data-stream via the dat a applied to the ?txpoh_n? input port. the user can configure the transmit sts-3c toh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 4 (sts-3c toh in sert) within the ?mapper control register ? byte 2?, as depicted below. mapper control register ? byte 2 (direct address = 0xn601) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sts-3 oh pass thru sts-3 remote loop-back sts-3 local loop-back sts-3 toh insert loop-timing poh pass thru unused r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 0 this step enables the ?transmit sts-3c toh processor? block (associated with channel ?n?) to accept its toh bytes via the ?txpoh input? port. step 2 ? write the value ?0? into bit 4 (f1 insert method) within the ?transmit sts-3c transport ? sonet transmit control register ? byte 1; as depicted below. transmit sts-3transport ? sonet transmit control register ? byte 1 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved e2 insert method e1 insert method f1 insert method s1 insert method k1k2 insert method m0m1 insert method[1] r/o r/o r/w r/w r/w r/w r/w r/w 0 0 x x 0 x x x this step configures the transmit sts-3c toh processo r block to use the ?txpoh input? port as the source for the f1 byte, within each outbound sts-3c frame. in this mode, the transmit sts-3 toh processor block will accept the value, corresponding to the f1 byte (via the ?txpoh_n? input port) and it will write this data into the f1 byte position, within the ?outbound? sts-3c frame. using the ?txpoh_n input? port to insert the f1 byte value into the ?outbound? sts-3c data-stream if the user intends to externally insert the f1 byte into the outbound sts-3c data-stream, via the ?txpoh_n? input port, then they must design some external circuitr y (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 70. figure 70 a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port?
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 321 txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt94l43 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in figure 70) is ?dashed? because this controlling this signal is not necessary if the user has executed ?step 2? above ? whenever the ?external circuit? samples the ?txpohframe_n? output pin ?high? and also the ?txpohenable_n? pin ?low?, then it should enter a ?wait state? (e.g., where it waits for __ periods of ?txpohclk_n? to elapse). afterwards, the external ci rcuit should exit this ?wait state? and then place the very first bit (e.g., the most significant bit) of the ?outbound? f1 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because t he f1 byte is the _ byte within the toh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the f1 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. figure 71 presents an illustration of the ?txpoh input interface? waveforms, when the ?external circuit? is writing the f1 byte into the ?txpoh input port?. figure 71 illustration of the ?txpoh i nput interface? waveforms, when th e ?external circuit? is writing the ?f1 byte? into the ?txpoh input port?
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 322 2.2.9.5.8 support/handling of the section dcc (d1, d2 and d3) bytes 2.2.9.5.9 support/handling of the k1/k2 bytes the transmit sts-3c toh processor block permits the user to control the value of the k1 and k2 bytes, which are to be transmitted via the ?outbound? sts-3c data-stream, by either or the following options. ? setting and controlling the k1, k2 bytes via software ? setting and controlling the k1, k2 bytes via the ?txpoh input port? the details and instructions for using eit her of these features are presented below. 2.2.9.5.9.1 setting and controlling the outbound k1, k2 bytes via software the transmit sts-3c toh processor block permits the us er to specify the contents of the k1 and k2 bytes within the outbound sts-3c data-stream via software command. the user can configure the transmit sts-3c toh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 1 (k1k2 method) within the ?transmit sts-3c transport ? sonet transmit control register ? byte 1, as depicted below. transmit sts-3transport ? sonet transmit control register ? byte 1 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved e2 insert method e1 insert method f1 insert method s1 insert method k1k2 insert method m0m1 insert method[1] r/o r/o r/w r/w r/w r/w r/w r/w 0 0 x x x x 1 x the step configures the transmit sts-3c toh proces sor block to read out the contents of the ?transmit sts-3c transport ? k1k2 ( aps) value registers (bytes 0 and 1), and l oad these values into the k1 and k2 byte positions within each outbound sts-3c data-stream. step 2 ? write the desired byte values (for the outbound k1 and k2 bytes) into the ?transmit sts-3c transport ? k1k2 (aps) value registers ? (bytes 0 and 1). the bit-format for these two registers is presented below. transmit sts-3 transport ? k1k2 (aps) value register ? byte 1 (address = 0x192e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_k2_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 transmit sts-3 transport ? k1k2 (aps) value register ? byte 1 (address = 0x192f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_k1_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 323 2.2.9.5.9.2 setting and controlling the outbound k1, k2 bytes via ?txpoh input port? the transmit sts-3c toh processor bl ock permits the user to specify the contents of the k1, k2 bytes within the ?outbound? sts-3c data-stream via the data applied to the ?txpoh_n? input port. the user can configure the transmit sts-3c toh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 4 (sts-3c toh in sert) within the ?mapper control register ? byte 2?, as depicted below. mapper control register ? byte 2 (direct address = 0xn601) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sts-3c oh pass thru sts-3c remote loop-back sts-3c local loop- back sts-3c toh insert loop-timing poh pass thru receive (ingress ) sts-3c enable transmit (egress) sts-3c enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 0 this step enables the ?transmit sts-3c toh processor? block (associated with channel ?n?) to accept its toh bytes via the ?txpoh input? port. step 2 ? write the value ?0? into bit 1 (k1k2 insert method) within the ?transmit sts-3c transport ? sonet transmit control register ? byte 1; as depicted below. transmit sts-3transport ? sonet transmit control register ? byte 1 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved e2 insert method e1 insert method f1 insert method s1 insert method k1k2 insert method m0m1 insert method[1] r/o r/o r/w r/w r/w r/w r/w r/w 0 0 x x x x 0 x this step configures the transmit sts-3c toh processo r block to use the ?txpoh input? port as the source for the k1, k2 bytes, within each outbound sts-3c fram e. in this mode, the transmit sts-3c toh processor block will accept the value, corresponding to the k1 and k2 bytes (via the ?txpoh_n? input port) and it will write this data into the k1 and k2 byte pos itions, within the ?outbound? sts-3c frame. using the ?txpoh_n input? port to insert the k1 and k2 byte values into the ?outbound? sts-3c data- stream if the user intends to externally insert the k1 and k2 into the outbound sts-3c data-stream, via the ?txpoh_n? input port, then they must design some exte rnal circuitry (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 72
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 324 figure 72 a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt94l43 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (in error! reference source not found. ) is ?dashed? because this controlling this signal is not necessary if the user has executed ?step 2? above. ? whenever the ?external circuit? samples the ?txpohframe_n? output pin ?high? and also the ?txpohenable_n? pin ?low?, then it should enter a ?wait state? (e.g., where it waits for __ periods of ?txpohclk_n? to elapse). afterwards, the external ci rcuit should exit this ?wait state? and then place the very first bit (e.g., the most significant bit) of the ?outbound? k1 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because the k1 and k2 are the _ and byte within the toh. ? afterwards, the ?external circuit? should serially pl ace the remaining fifteen bits (of the k1 and then k2 bytes) onto the ?txpoh_n? input pin, upon each of the next fifteen falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. figure 73 presents an illustration of the ?txpoh input interface? waveforms, when the ?external circuit? is writing the k1 and k2 bytes into the ?txpoh input port?. figure 73 illustration of the ?txpoh i nput interface? waveforms, when th e ?external circuit? is writing the ?k1 and k2 bytes? into the ?txpoh input port?
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 325 2.2.9.5.10 support/handling of the line dcc (d4 through d12) byte 2.2.9.5.11 support/handling of the s1 byte the transmit sts-3c toh processor block permits the user to control the value of the s1 byte, which is to be transmitted via the ?outbound? sts-3c data-s tream, by either or the following options. ? setting and controlling the s1 byte via software ? setting and controlling the s1 byte via the ?txpoh input port? the details and instructions for using eit her of these features are presented below. 2.2.9.5.11.1 setting and controlling the outbound s1 byte via software the transmit sts-3c toh processor block permits the user to specify the contents of the e1 byte within the outbound sts-3c data-stream via software command. the user can configure the transmit sts-3c toh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 2 (s1 insert method) within the ?transmit sts-3c transport ? sonet transmit control register ? byte 1, as depicted below. transmit sts-3transport ? sonet transmit control register ? byte 1 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved e2 insert method e1 insert method f1 insert method s1 insert method k1k2 insert method m0m1 insert method[1] r/o r/o r/w r/w r/w r/w r/w r/w 0 0 x x x 1 x x the step configures the transmit sts-3c toh proces sor block to read out the contents of the ?transmit sts-3c transport ? s1 byte value register, and load this value into the s1 byte position within each outbound sts-3c data-stream. step 2 ? write the desired byte values (for the outbound s1 byte) into the ?transmit sts-3c transport ? s1 byte value register. the bit-format for this register is presented below. transmit sts-3 transport ? transmit s1 byte value register (address = 0x193b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_s1_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.9.5.11.2 setting and controlling the outbo und s1 byte via ?txpoh input port? the transmit sts-3c toh processor block permits the user to specify the contents of the s1 byte within the ?outbound? sts-3c data-stream via the dat a applied to the ?txpoh_n? input port. the user can configure the transmit sts-3c toh pr ocessor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 4 (sts-3c toh insert ) within the ?mapper control register ? byte 2?, as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 326 mapper control register ? byte 2 (direct address = 0xn601) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sts-3c oh pass thru sts-3c remote loop-back sts-3c local loop- back sts-3c toh insert loop-timing poh pass thru receive (ingress) sts-3c enable transmit (egress) sts-3c enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 0 this step enables the ?transmit sts-3c toh processor? block (associated with channel ?n?) to accept its toh bytes via the ?txpoh input? port. step 2 ? write the value ?0? into bit 2 (s1 insert method) within the ?transmit sts-3 transport ? sonet transmit control register ? byte 1; as depicted below. transmit sts-3transport ? sonet transmit control register ? byte 1 (direct address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved e2 insert method e1 insert method f1 insert method s1 insert method k1k2 insert method m0m1 insert method[1] r/o r/o r/w r/w r/w r/w r/w r/w 0 0 x x x 0 x x this step configures the transmit sts-3c toh processo r block to use the ?txpoh input? port as the source for the s1 byte, within each outbound sts-3c frame. in this mode, the transmit sts-3c toh processor block will accept the value, corresponding to the s1 byte (via the ?txpoh_n? input port) and it will write this data into the s1 byte position, within the ?outbound? sts-3c frame. using the ?txpoh_n input? port to insert the s1 byte value into the ?outbound? sts-3c data-stream if the user intends to externally insert the s1 byte into the outbound sts-3c data-stream, via the ?txpoh_n? input port, then they must design some external circuitr y (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 74
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 327 figure 74 a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt94l43 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert the ?txpohins_n? line (in note: ) is ?dashed? because this controlling this signal is not necessary if the user has executed ?step 2? above. ? whenever the ?external circuit? samples the ?txpohframe_n? output pin ?high? and also the ?txpohenable_n? pin ?low?, then it should enter a ?wait state? (e.g., where it waits for __ periods of ?txpohclk_n? to elapse). afterwards, the external ci rcuit should exit this ?wait state? and then place the very first bit (e.g., the most significant bit) of the ?outbound? s1 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because t he s1 byte is the _ byte within the toh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the s1 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. figure 75 presents an illustration of the ?txpoh input interface? waveforms, when the ?external circuit? is writing the s1 byte into the ?txpoh input port?. figure 75 illustration of the ?txpoh i nput interface? waveforms, when th e ?external circuit? is writing the ?s1 byte? into the ?txpoh input port?
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 328 2.2.9.5.12 support/handling of the m1 byte 2.2.9.5.13 support/handling of the e2 byte the transmit sts-3 toh processor bloc k permits the user to control the value of the e2 byte, which is to be transmitted via the ?outbound? sts-3 data-str eam, by either or the following options. ? setting and controlling the e2 byte via software ? setting and controlling the e2 byte via the ?txpoh input port? the details and instructions for using eit her of these features are presented below. 2.2.9.5.13.1 setting and controlling the outbound e2 byte via software the transmit sts-3 toh processor bloc k permits the user to specify the c ontents of the e2 byte within the outbound sts-3 data-stream via software command. the user can configure the transmit sts-3 toh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 5 (e2 insert method) within the ?transmit sts-3 transport ? sonet transmit control register ? byte 1, as depicted below. transmit sts-3transport ? sonet transmit control register ? byte 1 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved e2 insert method e1 insert method f1 insert method s1 insert method k1k2 insert method m0m1 insert method[1] r/o r/o r/w r/w r/w r/w r/w r/w 0 0 1 x x x x x the step configures the transmit sts-3 toh processor block to read out the contents of the ?transmit sts- 3 transport ? e2 byte value register, and load this va lue into the e2 byte position within each outbound sts-3 data-stream. step 2 ? write the desired byte values (for the outbound e2 byte) into the ?transmit sts-3 transport ? e2 byte value register. the bit-format for this register is presented below. transmit sts-3 transport ? transmit e2 byte value register (address = 0x1947) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit_e2_byte_value[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.2.9.5.13.2 setting and controlling the outbo und e2 byte via ?txpoh input port? the transmit sts-3 toh processor block permits the user to specify the contents of the e2 bytes within the ?outbound? sts-3 data-stream via the dat a applied to the ?txpoh_n? input port. the user can configure the transmit sts-3 toh proc essor block to accomplish this by performing the following steps. step 1 ? write the value ?1? into bit 4 (sts-3 toh insert) within the ?mapper control register ? byte 2?, as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 329 mapper control register ? byte 2 (direct address = 0xn601) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sts-3 oh pass thru sts-3 remote loop-back sts-3 local loop-back sts-3 toh insert loop-timing poh pass thru receive (ingress) sts-1 enable transmit (egress) sts-1 enable r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 0 this step enables the ?transmit sts-3 toh processor? block (associated with c hannel ?n?) to accept its toh bytes via the ?txpoh input? port. step 2 ? write the value ?0? into bit 1 (e2 insert method) within the ?transmit sts-3c transport ? sonet transmit control register ? byte 1; as depicted below. transmit sts-3transport ? sonet transmit control register ? byte 1 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 reserved e2 insert method e1 insert method f1 insert method s1 insert method k1k2 insert method m0m1 insert method[1] r/o r/o r/w r/w r/w r/w r/w r/w 0 0 0 x x x x x this step configures the transmit sts-3 toh processor block to use the ?txpoh input? port as the source for the e2 byte, within each outbound sts-3c frame. in this mode, the transmit sts-3c toh processor block will accept the value, corresponding to the e2 byte (via the ?txpoh_n? input port) and it will write this data into the e2 byte position, within the ?outbound? sts-3c frame. using the ?txpoh_n input? port to insert the e2 byte value into the ?outbound? sts-3c data-stream if the user intends to externally insert the e2 byte into the outbound sts-3c data-stream, via the ?txpoh_n? input port, then they must design some external circuitr y (which can be realized in an asic, fpga or cpld solution) to do to the following. ? continuously sample the ?txpohenable_n? and t he ?txpohframe_n? output pins upon the rising edge of the ?txpohclk_n? output clock signal. a simple illustration of this ?external circuit? being interfaced to the ?txp oh input port? is presented below in figure 76.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 330 figure 76 a simple illustration of the ?external circ uit? being interfaced to the ?txpoh input port? txpoh_n txpohclk_n txpohframe_n txpohenable_n txpohins_n xrt94l43 device external circuit txpohclk_in txpohframe_in txpohdata_out txpohenable_in txpoh_insert note: the ?txpohins_n? line (infigure 76) is ?dashed? because this controlling this signal is not necessary if the user has executed ?step 2? above. ? whenever the ?external circuit? samples the ?txpohframe_n? output pin ?high? and also the ?txpohenable_n? pin ?low?, then it should enter a ?wait state? (e.g., where it waits for __ periods of ?txpohclk_n? to elapse). afterwards, the external ci rcuit should exit this ?wait state? and then place the very first bit (e.g., the most significant bit) of the ?outbound? e2 byte onto the ?txpoh_n? input pin, upon the very next falling edge of ?txpohclk_n?. this data bit will be sampled and latched into the ?transmit sts-3c poh processor? block circuitry, upon the very next rising edge of ?txpohclk_n?. note: this ?wait state? period is necessary because t he e2 byte is the _ byte within the toh. ? afterwards, the ?external circuit? should serially place the remaining seven bits (of the e2 byte) onto the ?txpoh_n? input pin, upon each of the nex t seven falling edges of ?txpohclk_n?. ? the ?external circuit? should then revert back to continuously sampling the states of the ?txpohenable_n? and ?txpohframe_n? output pins and r epeat the above-mentioned process. figure 77 presents an illustration of the ?txpoh input interface? waveforms, when the ?external circuit? is writing the e2 byte into the ?txpoh input port?. figure 77 illustration of the ?txpoh i nput interface? waveforms, when th e ?external circuit? is writing the ?e2 byte? into the ?txpoh input port?.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 331 2.2.9.5.14 scrambling data the transmit sts-3 toh processor block permits the user to either enable or disable scrambling of the sts- 3 data, prior to it being transmitted to the remote terminal equipment. the customer can accomplish this by writing the appropriate value into bit 2 (scramble e nable), within the transmit sts-3 transport ? sonet transmit control register, as depicted below. transmit sts-3 transport ? sonet transmit control register ? byte 0 (address = 0x1902) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 m0m1 insert method[0] unused rdi-l force ais-l force los force scramble enable b2 error insert a1a2 error insert r/w r/o r/w r/w r/w r/w r/w r/w 0 0 0 0 0 x 0 0 setting this bit-field to ?1? enables the scrambler. conversely, setting this bit-field to ?0? disables the scrambler. if the scrambler is enabled, then it will scramble the ?outbound? sts-3 data with a generating polynomial of x 7 + x 6 + 1 and a sequence length of 127. 2.3 receive direction if a given channel (or the entire device) is configured to operate in the atm mode, then the purpose of the receive section within the xrt94l33 1-channel sts-3c /sts-3 atm uni device is to permit a local atm layer (or atm adaptation layer ) processor to receive atm cell data from a remote piece of equipment via an sts-3, sts-3c or ds3/e3 transport medium. for atm uni applications, the receive section of th e xrt94l33 chip consists of the following blocks. ? receive sts-3 toh processor block ? receive sts-3c poh processor block (for sts-3c applications) ? receive sonet poh processor block (for sts-3 applications) ? receive atm cell processor block ? receive utopia interface block the receive sts-3 toh proces sor block will receive an sts-3 signal, ei ther over the pecl interface or via the receive sts-3 telecom bus interface. as the re ceive sts-3 toh processor block receives this signal, it will do the following. ? it will locate the boundaries of the incoming sts-3 frames ? it will compute and verify the b1 and b2 bytes ? it will detect and clear the los, sef, lof, rdi-l and ais-l defect condition ? it will detect and flag rei-l events ? it will detect and clear the sd and sf conditions ? it will route the sts-3c spe data to the receive sts-3c poh processor blo ck for further processing. the receive sts-3c poh processor block will receive the sts-3c spe data from the receive sts-3 toh processor block. as the receive st s-3c poh processor block receives this signal, it will do the following. ? it will compute and verify the b3 bytes ? it will detect and clear the lop-p, rdi-p and ais-p defect conditions
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 332 ? it will detect and flag rei-p events ? it will detect and clear the uneq-p, plm-p and tim-p conditions ? it will declare and clear the lop-c and ais-c conditions. finally, the receive sts-3c poh processor block will extract out the payload data from each incoming sts- 3c spe, and will route this data to ei ther the receive atm cell processor block (for atm uni applications) or the receive ppp packet processor block (for ppp applications). for atm applications the receive atm cell processor block will receive a c ontinuous stream of un-framed atm cells, and will perform the following functions on this incoming data-stream. ? cell delineation ? hec byte verification ? idle cell filtering ? user cell filtering ? parity calculation and insertion afterwards, the receive atm cell proces sor block will route all cells (which have satisfactorily survived the above-mentioned processing) to the rx fifo, within the receive utopia interface block. the atm layer processor will read ou t the contents of these atm cells via the receive utopia interface block of the xrt94l33. the receive utopia inte rface block provides the industry-standard atm/phy interface functions. the receive utopia interface bl ock will also provide signaling to support data-flow control between the atm layer processor and the receive utopia interface block. the receive section of the xrt94l33 is discussed in considerable detail below. for ppp applications the receive ppp packet processor bloc k will receive a continuous str eam of un-framed ppp packets, and will perform the following functions on this incoming data-stream. ? crc-16/32 checking ? byte-de-stuffing 2.3.1 receive sts-3 toh processor block the purpose of the receive sts-3 toh processor block is to accomplish the following. ? to receive an sts-3 data-stream from the remote lt e, via an optical transceiver or the system back- plane (through the receive pecl interface) or via the receive sts-3 telecom bus interface. ? to acquire and maintain frame synchronization with the incoming sts-3 data-stream ? to optionally de-scramble the incoming sts-3 data-stream. ? to compute and verify the b1 and b2 bytes and increm ent performance monitor regi sters anytime it detects b1 and b2 byte errors. ? to declare and clear the following defect conditions - los (loss of signal) - sef (severely errored frame) - lof (loss of frame) - ais-l (line ais)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 333 - rdi-l (line ? remote defect indicator) - sd (signal degrade) - sf (signal fail) ? to increment performance monitor regi sters anytime it detects an rei-l event. ? to (optionally) automatically transmit the ais-p (path ais) indicator, dow nstream (e.g., towards the receive sts-3c poh processor block) upon declaration of the following defect conditions. - los - lof - sd - sf - ais-l finally, the receive sts-3 toh processor block will r oute sts-3c spes to its co rresponding receive sts- 3c poh processor block. figure 78 presents an illustration of t he functional block diagram of the xrt94l33 atm uni/ppp ic; with the ?receive sts-3 toh processor? block highlighted. figure 78 illustration of the func tional block diagram of the xr t94l33 atm uni/ppp ic; with the receive sts-3 toh processor block highlighted transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3/12 toh processor block receive sts-3/12 toh processor block transmit sts-3/12 toh processor block transmit sts-3/12 toh processor block receive sts-3/12 poh processor block receive sts-3/12 poh processor block transmit sts-3/12 poh processor block transmit sts-3/12 poh processor block sts-3/12 telecom bus interface block sts-3/12 telecom bus interface block sts-3/12 pecl interface block sts-3/12 pecl interface block sts-3/12 cdr block sts-3/12 cdr block xrt95l34 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block the operation of the ?receive sts-3 toh processor? block is discussed in some detail below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 334 the receive sts-3 toh processor block can be conf igured to receive the incoming sts-3 data via the receive sts-3 pecl interface block or via the receiv e sts-3 telecom bus interface block. a detailed discussion on the receive sts-3 pecl interface block can be found in section 8.0. likewise, a detailed discussion on the receive sts-3 telecom bu s interface can be found in section 7.0. 2.3.1.1 descrambling of data the receive sts-3 toh processor block permits the user to optionally descramble the incoming sts-3 data-stream. 2.3.1.2 los declaration and clearance criteria sonet r equirements for d eclaring the los d efect according to telecordia gr-253-core, a sonet network element must monitor all incoming sonet signals (before de-scrambling) for an ?all zeros? pattern. the network element must declare an los condition whenever it continues to receives an ?all zeros? pattern for 100 s or longer. further, the network element must not declare an los condition, if it receives the ?all zeros? pattern for 2.3 s or less. 2.3.1.2.1 how the receive sts-3c toh pr ocessor block declares the los defect the receive sts-3c toh processor block is capable of de claring and clearing the los condition. further, the receive sts-3c toh processor bloc k register set permits the user to define the los declaration criteria, by writing the appropriate data into the ?receive sts-3c transport ? los threshold value ? msb? and ?lsb? registers, as illustrated below. receive sts-3c transport ? los threshold value - msb (address = 0x112e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 los_threshold[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3c transport ? los threshold value - lsb (address = 0x112f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 los_threshold[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 the contents of these two registers, combined, reflects the number of consecutive ?all zeros? bytes (prior to de-scrambling) that the receive sts- 3 toh processor block must detect before it declares the los defect condition. for sts-3c applications, if the user wishes to comply with the los declaration requirements, per telecordia gr-253-core, then they must writ e a value that ranges between 0x000f and 0x0288 into the ?receive sts- 3 transport ? los threshold value ? msb/lsb? register. if the receive sts-3c toh processor block detects the app ropriate number of consecut ive ?all zeros?, then it will declare the los defect condition. the receive sts-3c toh processo r block will indicate that it is declaring the los defect condition, by doing all of the following. ? it will set bit 0 (los defect declar ed) within the receive sts-3 transport status register ? byte 0, to ?1? as illustrated below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 335 receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect declared k1, k2 byte unstable defect declared sf defect declared sd defect declared lof defect declared sef defect declared los defect declared r/o r/o r/o r /o r/o r/o r/o r/o 0 0 0 0 0 0 0 1 ? it will generate the ?change of los defect condition? interrupt, by toggling the ?int*? output pin ?low?, and by setting bit 0 (change of los defect condition inte rrupt status), within the ?receive sts-3 transport interrupt status register ? byte 0? to ?1?, as illustrated below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 1 2.3.1.2.2 how the receive sts-3 toh processor block clears the los defect the receive sts-3 toh processor block will clear the los defect once both of the following conditions have been met. that the receive sts-3 toh processor block detects proper a1 and a2 bytes in two consecutive sts-3 frames, and that, in between the detection of the two sets of a1 /a2 bytes, the receive sts-3 toh processor block does not detect the ?los_threshold[15:0]? number of ?all ze ro? bytes, within the incoming sts-3 data-stream. once the receive sts-3 toh processor bl ock clears the los defect, it will no tify the system of this fact by doing the following. ? it will set bit 1 (los detected) within the receive st s-3c transport status regist er ? byte 0? to ?0? as illustrated below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect declared k1, k2 byte unstable defect declared sf defect declared sd defect declared lof defect declared sef defect declared los defect declared r/o r/o r/o r /o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 ? it will generate the ?change of los defect condition? in terrupt by toggling the ?int *? output pin ?low?, and by setting bit 0 (change of los defect condition inte rrupt status), within the ?receive sts-3 transport interrupt status register ? byte 0? to ?1?, as illustrated below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 336 receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 1 2.3.1.2.3 configuring the transmit sts-3 toh pro cessor block to automatically transmit the rdi-l indicator whenever the receive sts-3 toh processor block declares the los defect condition the user can configure the transmit sts-3 toh proc essor block to automatica lly transmit the rdi-l indicator whenever (and for the duration that) the corresponding receive sts-3 toh processor block declares the los defect condition. figure 79 presents an illustration of the transmit sts-3 toh processor block transmi tting the rdi-l indicator (up-stream) towards the remote lte whenever the co rresponding receive sts-3 toh processor block is declaring the los defect condition. figure 79 illustration of the transmit sts-3 toh pr ocessor block transmitting the rdi-l indicator to the remote lte whenever the corresponding receive sts-3 toh processor block is declaring the los defect condition the user can implement this configuration by setting bit 0 (transmit rdi-l upon los) within the ?transmit sts-3 transport ? rdi-l control register, as depicted below. transmit sts-3 transport ? rdi-l control register (address = 0x1933) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused external rdi-l enable transmit rdi-l upon ais transmit rdi-l upon lof transmit rdi-l upon los r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 1
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 337 2.3.1.2.4 configuring the receive sts-3 toh process or block to automatically transmit the ais-p indicator, in the downstream direction (towards the receive sts-3c poh processor blocks) whenever it declares the los defect condition the user can configure the receive sts-3 toh proc essor block to automatically transmit the ais-p indicator, in the down-stream direction (towards t he corresponding receive sts-3c poh processor block) whenever (and for the duration that) it declares the los defect condition. note: if the xrt94l33 is configured to operate in either th e ?1-channel sts-3 atm uni/ppp? mode, then the receive sts-3 toh processor block will trans mit the ais-p indicator to all three receive sonet poh processor blocks, in parallel, whenever it declares the los defect condition. figure 80 presents an illustration of t he receive sts-3 toh processor bloc k transmitting the ais-p indicator, in the down-stream direction (towards the receive st s-3c poh processor block) whenever it declares the los defect condition. figure 80 an illustration of the receive sts-3 toh processor block transmitting the ais-p indicator, in the down-stream direction (towards the receive sts-3c poh processor blocks) whenever it declares the los defect condition transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3/12 toh processor block receive sts-3/12 toh processor block transmit sts-3/12 toh processor block transmit sts-3/12 toh processor block receive sts-3/12 poh processor block receive sts-3/12 poh processor block transmit sts-3/12 poh processor block transmit sts-3/12 poh processor block sts-3/12 telecom bus interface block sts-3/12 telecom bus interface block sts-3/12 pecl interface block sts-3/12 pecl interface block sts-3/12 cdr block sts-3/12 cdr block xrt95l34 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block los ais-p the user can implement this configuration by setting bits 1 (transmit ais-p [down-stream] upon los) and 0 (auto ais), within the ?receive sts-3 transport ? au to ais control? register, to ?1? as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 338 receive sts-3 transport ? auto ais control register (address = 0x1163) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit ais-p (down- stream) upon section trace message unstable transmit ais-p (down- stream) upon section trace message mismatch transmit ais-p (down- stream) upon sf transmit ais-p (down- stream) upon sd transmit ais-p (down- stream) upon loss of optical carrier transmit ais-p (down- stream) upon lof transmit ais-p (down- stream) upon los auto ais r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 1 1 of course, if the receive sts-3 toh processor bloc k transmits the ais-p indicator towards the receive sts-3c poh processor block, then all of the following will happen. ? the receive sts-3c poh processor bloc k will declare the ais-p defect condition. ? the corresponding receive atm cell processor block will declare t he lcd (loss of cell delineation) defect condition. 2.3.1.3 receive sts-3 toh proc essor block fram ing alignment at any given time, the receive sts-3 toh processor bl ock is operating in either one of the following ?framing alignment? modes. ? in-frame ? sef = 1, lof = 0 ? sef = 1, lof = 1 ? sef = 0, lof = 1 the receive sts-3 toh processor block will transition through these various modes depending upon whether or not it has framing alignment with the a1, a2 bytes within the incoming sts-3 frames. each of these ?framing alignment? modes will be discussed in some detail below. the overall framing alignment state-machine (within the receive sts-3 toh proces sor block) is as presented below in figure 81.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 339 figure 81 illustration of the ?receive sts-3 toh pr ocessor? block framing a lignment state-machine sef = 1 lof = 1 sef = 1 lof = 1 sef = 1 lof = 0 sef = 1 lof = 0 in frame state in frame state framing byte errors detected in 4 consecutive sonet frames un-erred framing bytes are detected in a ?user-selectable? number of consecutive sonet frames framing byte errors detected in 3 (or less) consecutive sonet frames sef = 0 lof = 1 sef = 0 lof = 1 sef defect persists for 3ms. un-erred framing bytes are detected in 2 consecutive sonet frames un-erred framing bytes are detected in 2 consecutive sonet frames 2.3.1.3.1 the ?sef = 1, lof = 1? state when the xrt94l33 first powers up, the receive sts-3 toh processor block will be operating in this state. in this case, both the lof (loss of frame) and t he sef (severely erred frame) defect conditions are declared. the receive sts- 3 toh processor block will indicate this fact by setting both bi ts 2 (lof defect declared) and 1 (sef defect declared), within the ?rec eive sts-3 transport status register ? byte 0? as depicted below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect declared k1, k2 byte unstable defect declared sf defect declared sd defect declared lof defect declared sef defect declared los defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 1 1 0 the receive sts-3 toh proces sor block will remain in th is condition until it receiv es two consec utive sts-3 frames that contain no framing byte errors. at this point the receive sts-3 to h processor block will clear the sef defect and will transition into the ?sef = 0, lof = 1? state. as the receive sts-3 toh processor block transitions fr om the ?sef = 1, lof = 1? state to the ?sef = 0, lof = 1? state, it will do all of the following.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 340 it will clear bit 1 (sef defect declared ) within the ?receive sts- 3 transport status regist er ? byte 0? to ?0?, as depicted below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect declared k1, k2 byte unstable defect declared sf defect declared sd defect declared lof defect declared sef defect declared los defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 1 0 0 5. it will generate the ?change in sef defect condition? interrupt. the xrt94l33 will indicate that it is generating this interrupt by doing the following. toggling the ?int*? input pin ?low? and setting bit 1 (change of sef defect condition interr upt status), within the ?receive sts-3 transport interrupt status register ? byte 0? as depicted below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 0 0 1 0 2.3.1.3.2 the sef = 0, lof = 1 state once the receive sts-3 toh processor block reaches this state, then it has already cleared the ?sef defect condition?. for the duration that the receive sts-3 toh processor block is operating in the ?sef = 0, lof = 1? state, the receive st s-3 toh processor block will be test ing the framing a lignment bytes (a1 and a2) within the incoming sts-3 signal, in order to determine if it can clear the ?lof? defect condition. in this case, the receive sts-3 toh processor will test the framing alignment bytes (within the incoming sts-3 data-stream) a ?user-selectable? number of sonet frame periods. if the receive sts-3 toh processor does not detect any framing byte errors (during this ?user-selected test? period), then it will clear the lof defect. the user can specify the number of consecutive sts-3 frame periods, that the receive sts-3 toh processor block must remain in the ?sef = 0, lof = 1? state, by writ ing the appropriate value into bits 3 through 0 (in-sync threshold[3:0]) within the receive sts-3 transport ? in sync threshold register; as depicted below. receive sts-3 transport ? in sync threshold register (address = 0x112b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused in-sync threshold[3:0] r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x x x x
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 341 the value that the user writes into these bit-fields reflects the number of sts-3 frame periods that the receive sts-3 toh processor block must reside within the ?sef = 0, lof = 1? state and test the framing alignment bytes, within the incoming sts-3 data-stream. if the receive sts-3 toh processor block does not det ect the ?user selectable? number of consecutive ?un- erred? sts-3 frames, then it will remain in the ?sef = 0, lof = 1? state and will continue to test for the ?user- selectable? number of consecutive un-erred sts-3 frame. if the receive sts-3 toh processor block were to detect framing byte errors in four consecutive sts- 3 frames, then it will declare the ?sef? defect and will transition back into the ?sef = 1, lof = 1? state. if the receive sts-3 toh processor bl ock receives this ?user-selectable? number of consecutive ?unerred? sts-3 frames, then it will clear the ?lof defect? and will transition into the ?in-frame? state. as the receive sts-3 toh processor bl ock transitions from the ?sef = 0, lof = 1? state to the ?in-frame? state, it will do all of the following. it will clear bit 2 (lof defect declared) within the ?recei ve sts-3 transport status r egister ? byte 0? to ?0? as depicted below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect declared k1, k2 byte unstable defect declared sf defect declared sd defect declared lof defect declared sef defect declared los defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 it will generate the ?change in lof defect condition? interrupt. the xrt94l33 will indicate that it is generating this interrupt by doing the following. a. toggling the ?int*? input pin ?low?. b. setting bit 2 (change of lof defect condition interrupt status), within the ?receive sts-3 transport interrupt status regist er ? byte 0? as depicted below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 0 0 1 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 342 2.3.1.3.3 the in-frame state once the receive sts-3 toh processor block reaches th is state, it is considered to be operating in a ?normal? manner. in this mode, the receive sts-3 toh processor block will continue to monitor and check the value of the framing alignment bytes wi thin the incoming sts-3 data-stream. in general, the receive sts-3 toh processor block will be tolerant to some occasional framing byte errors. however, if the receive sts-3 toh processor block were to detect framing alignment bit errors in four consecutive sonet frames (within the incoming sts-3 data-strea m), then it will declare the ?sef? defect. as the receive sts-3 toh proces sor declares the sef defect, then it will transition into the ?sef = 1, lof = 0? state. as the receive sts-3 toh processor block transitions from the ?in-frame? to the ?sef = 1, lof = 0? state, it will do all of the following. 5. it will set bit 1 (sef defect declared) within the ?receive sts-3 transport st atus register ? byte 0? to ?1?, as depicted below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect declared k1, k2 byte unstable defect declared sf defect declared sd defect declared lof defect declared sef defect declared los defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 1 0 6. it will generate the ?change of sef defect condition? interrupt. the xrt94l33 will indicate that it is generating this interrupt by doing the following. a. toggling the ?int*? input pin ?low? and b. setting bit 1 (change of sef defect condition inte rrupt status), within the ?receive sts-3 transport interrupt status register ? byte 0? as depicted below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 0 0 1 0 2.3.1.3.4 the sef = 1, lof = 0 state once the receive sts-3 toh processor block reaches this state, then it has already declared the ?sef defect condition?. for the duration that the receive sts-3 toh processor block is operating in the ?sef = 1, lof = 0? state, the receive st s-3 toh processor block will be test ing the framing a lignment bytes (a1 and a2) within the incoming sts-3 signal, in order to determine if it should declare the ?lof? or the ?in- frame? condition.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 343 if the receive sts-3 toh processor block receives two consecutive sonet fram es that do have contain any framing alignment byte errors, then it will clear the sef defect and will transition back into the ?in- frame? state. on the other hand, if the receive sts-3 toh processor continues to detect incoming sonet frames (with framing alignment errors) then it w ill continue to declare the ?sef? defect. if the receive sts-3 toh processor block continues to declare t he ?sef defect? for at least 3ms, then it will declare the ?lof defect?. at this time, the receive sts-3 toh processor block will transition back into the ?sef = 1, lof = 1? state. the ?sef? and ?lof? declaration and clearance criteria are summarized, in some detail below. 2.3.1.3.5 the sef (severely erred frame) defect declarat ion and clearance criteria the receive sts-3 toh processor block is capable of declaring and clearing the sef (severely erred frame) defect condition; as described below. 2.3.1.3.5.1 how the receive sts-3 toh pr ocessor block declares the sef defect the receive sts-3 toh processor block will declare t he sef defect condition anytime it detects framing byte (a1 and a2) errors in four consecutive frames. whenever the receive sts- 3 toh processor block declares the sef defect condition, then it will do the following. 1. it will indicate that it is declaring the sef defec t condition by setting bit 1 (sef defect declared), within the receive sts-3 transport status regi ster ? byte 0? to ?1?, as depicted below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect declared k1, k2 byte unstable defect declared sf defect declared sd defect declared lof defect declared sef defect declared los defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 1 0 2. it will generate the ?c hange of sef defect condition interrupt ?. the receive sts-3 toh processor block will indicate that it is declaring the ?chan ge of sef defect conditi on? interrupt by doing the following. a. toggling the ?int*? output pin ?low?. b. b. setting bit 1 (change of sef defect condit ion interrupt status), within the receive sts-3 transport interrupt status register ? byte 0? to ?1?, as illustrated below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 0 0 1 0 2.3.1.3.5.2 how the receive sts-3 toh processor block clears the sef defect condition
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 344 once the receive sts-3 toh processor block declares the sef defect condition, then it will clear the sef defect condition if it detects 2 cons ecutive sts-3 frames with un-erred fr aming alignment (a1 and a2) bytes. once the receive sts-3 toh proces sor block clears the sef defect c ondition, then it will alert the microprocessor of this fact by doing the following. 7. it will indicate that it is clearing the sef defect c ondition by setting bit 1 (sef defect declared), within the receive sts-3 transport status register ? byte 0? to ?0? as depicted below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect declared k1, k2 byte unstable defect declared sf defect declared sd defect declared lof defect declared sef defect declared los defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 8. it will generate the ?change of sef defect conditi on? interrupt. the receive sts-3 toh processor block will indicate that it is declaring the ?change of sef defect condition? interrupt by doing the following. a. toggling the ?int*? output pin ?low?. b. b. setting bit 1 (change of sef defect condit ion interrupt status), within the receive sts-3 transport interrupt status register ? byte 0? to ?1?, as illustrated below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 0 0 1 0 2.3.1.3.6 the lof (loss of frame) declaration and clearance criteria the receive sts-3 toh processor block is capable of declaring and clearing the lof (loss of frame) defect condition, as described below. 2.3.1.3.6.1 how the receive sts-3 toh process or block declares the lof defect condition the receive sts-3 toh processor block will declare the lof defect anytime the receive sts-3 toh processor block continuously declares the sef defect condition for at least 3ms. whenever the receive sts-3 toh processor block decl ares the lof defect condition, then it will do the following. 9. it will indicate that it is declaring the lof de fect condition by setting bit 2 (los defect declared) within the ?receive sts-3 transport status re gister ? byte 0? to ?1? as depicted below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l s1 b y te k1, k2 b y te sf defect sd defect lof defect sef defect los defect
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 345 defect declared unstable defect declared unstable defect declared declared declared declared declared declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 1 0 0 10. it will generate the ?change of lof defect conditi on? interrupt. the receive sts-3 toh processor block will indicate that it is declaring the ?change of lof defect condition? interrupt by doing the following. a. toggling the ?int*? output pin ?low?. b. setting bit 2 (change of lof defect condition interrupt status) within the receive sts-3 transport interrupt status register ? byte 0 to ?1? as depicted below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 0 1 0 0 2.3.1.3.6.2 how the receive sts-3 toh process or block clears the lof defect condition once the receive sts-3 toh processor block has decla red the lof defect condition, then it will clear the lof only after both of the following conditions have been met. 11. that the receive sts-3 toh proces sor block has cleared the sef defect. 12. if it detects a ?user-specified? number of consecutive sts-3 frames with un-erred framing alignment (e.g., a1 and a2) bytes. the user can specify the ?lof clearance criteria? by writing the appropriate value (in terms of numbers of consecutive sts-3 frames with un-erred a1 and a2 bytes) into bits 3 through 0 (in-sync threshold) within the ?receive sts-3 transport ? in sync threshold? register, as depicted below. receive sts-3 transport ? in-sync threshold value (address =0x112b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused frpatout[1:0] frpatin[1:0] unused r/o r/o r/o r/w r/w r/w r/w r/o 0 0 0 0 0 0 0 0 once the receive sts-3 toh processor block has clea red the sef defect, then it will proceed to check for the occurrence of ?in-sync thres hold[3:0]? number of incoming sts-3 fr ames that contain un-erred a1 and a2 bytes. once all of this ha s occurred then the receive sts-3 toh processor block will clear the lof defect condition. once the receive sts-3 toh processor block clears the lof condition, then it will alert the microprocessor of this fact by doing the following. 13. it will indicate that it is clearing the lof defect condition by setting bit 2 (lof defect declared) within the receive sts-3 transport status register ? byte 0? to ?0? as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 346 receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect declared k1, k2 byte unstable defect declared sf defect declared sd defect declared lof defect declared sef defect declared los defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 14. it will generate the ?change of lof defect condition ? interrupt. the receive sts-3 toh processor block will indicate that it is declaring the ?change of lof defect condition? interrupt by doing the following. c. toggling the ?int*? output pin ?low?. setting bit 2 (change of lof defect condition interrupt st atus) within the receive sts-3 transport interrupt status register ? byte 0 to ?1? as depicted below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 0 1 0 0 2.3.1.3.6.3 configuring the transmit sts-3 toh processor block to automatically transmit the rdi-l indicator whenever the receive st s-3 toh processor block declares the lof defect condition the user can configure the transmit sts-3 toh proc essor block to automatica lly transmit the rdi-l indicator to the remote lte whenever (and for th e duration that) the corresponding receive sts-3 toh processor block declares the lof defect condition. figure 82 presents an illustration of the transmit sts-3 toh processor block transmitting the rdi-l indicator, to the remote lte, whenever the correspo nding receive sts-3 toh processor block declares the lof defect condition. figure 82 illustration of the transmit sts-3 to h processor block (wit hin a given xrt94l33) transmitting the rdi-l indicator, to the remote lte whenever the corresponding receive sts-3 toh processor block declares the lof defect condition. the user can implement this configuration by setting bit 1 (transmit rdi-l upon lof) within the transmit sts-3 transport ? rdi-l control register, as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 347 transmit sts-3 transport ? rdi-l control register (address = 0x1933) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused external rdi-l enable transmit rdi-l upon ais-l transmit rdi-l upon lof transmit rdi-l upon los r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 1 0 2.3.1.3.6.4 configuring the receive sts-3 toh pro cessor block to automatically transmit the ais- p indicator in the down-stream direction (towards the receive sts-3c poh processor block) whenever it declares the lof defect the user can configure the receive sts-3 toh proc essor block to automatically transmit the ais-p indicator, in the down-stream direction (towards t he corresponding receive sts-3c poh processor block) whenever (and for the duration that) it declares the lof defect condition. note: if the xrt94l33 is configured to operate in either th e ?1-channel sts-3 atm uni/ppp? mode, then the receive sts-3 toh processor block will transmit the ais-p indica tor to all four receive sonet poh processor blocks, in parallel, whenever it dec lares the lof defect condition. figure 83 presents an illustration of t he receive sts-3 toh processor bloc k transmitting the ais-p indicator, in the down-stream direction (towards the receive st s-3c poh processor block) whenever it declares the lof defect condition. figure 83 an illustration of the receive sts-3 toh processor block transmitting the ais-p indicator, in the down-stream direction (towards the receive sts-3c poh processor blocks) whenever it declares the lof defect condition
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 348 transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3/12 toh processor block receive sts-3/12 toh processor block transmit sts-3/12 toh processor block transmit sts-3/12 toh processor block receive sts-3/12 poh processor block receive sts-3/12 poh processor block transmit sts-3/12 poh processor block transmit sts-3/12 poh processor block sts-3/12 telecom bus interface block sts-3/12 telecom bus interface block sts-3/12 pecl interface block sts-3/12 pecl interface block sts-3/12 cdr block sts-3/12 cdr block xrt95l34 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block lof ais-p the user can implement this configuration by setting bits 2 (transmit ais-p [down-stream] upon lof) and 0 (auto ais), within the ?receive sts-3 transport ? au to ais control? register, to ?1? as depicted below. receive sts-3 transport ? auto ais control register (address = 0x1163) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit ais-p (down- stream) upon section trace message unstable transmit ais-p (down- stream) upon section trace message mismatch transmit ais-p (down- stream) upon sf transmit ais-p (down- stream) upon sd transmit ais-p (down- stream) upon loss of optical carrier transmit ais-p (down- stream) upon lof transmit ais-p (down- stream) upon los auto ais r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 1 0 1 of course, if the receive sts-3 toh processor bloc k transmits the ais-p indicator towards the receive sts-3c poh processor block, then all of the following will happen. ? the receive sts-3c poh processor bloc k will declare the ais-p defect condition. ? the corresponding receive atm cell processor block will declare t he lcd (loss of cell delineation) defect condition. 2.3.1.4 the ais-l (line ais) defect declaration and clearance criteria
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 349 according to telecordia gr-253-core, a line termi nating equipment must declare the ais-l (line ais) defect condition whenever it determines that bits 6, 7 and 8 (within the k2 byte) of the incoming sts-3 data- stream, are each set to ?1? for fi ve consecutive sts-3 frames. figure 84 presents an illustration of the ?ais-l defect declarat ion/clearance? state machine diagram that is used by the receive sts-3 toh proc essor blocks within the xrt94l33. figure 84 illustration of the ?ais-l defect decl aration/clearance? state machine diagram ais-l defect is cleared ais-l defect is cleared ais-l defect is declared ais-l defect is declared receive sts-3/sts-12 toh processor block receives five (5) consecutive frames in which bits 6, 7 and 8 (within the k2 byte) are set to the pattern [1, 1, 1] receive sts-3/sts-12 toh processor block receives five (5) consecutive frames in which bits 6, 7, and 8 (within the k2 byte) are not set to the pattern [1, 1, 1] 2.3.1.4.1 how the receive sts-3 toh processor block declares the ais-l defect condition the receive sts-3 toh processor bloc k is capable of declaring and cleari ng the ais-l defect condition. if the receive sts-3 toh processor block receives at least five consecutive sts-3 frames, in which bits 6, 7 and 8 (within the k2 byte) are each set to ?1?, then it will declare the ais-l defect condition. the receive sts-3c toh processor block will indica te that it is declaring the ais-l defect condition, by doing all of the following. ? it will set bit 0 (ais-l defect declared) within the re ceive sts-3 transport status register ? byte 1, to ?1? as illustrated below. receive sts-3 transport status register ? byte 1 (address = 0x1106) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused section trace message mismatch defect declared section trace message unstable defect declared ais_l defect declared
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 350 r/o r/o r/o r /o r/o r/o r/o r/o 0 0 0 0 0 0 0 1 ? it will generate the ?change of ais-l defect condition? interrupt, by toggling the ?int*? output pin ?low?, and by setting bit 1 (change of ais-l defect condition in terrupt status) within the ?receive sts-3 transport interrupt status register ? byte 2? to ?1?, as illustrated below. receive sts-3 transport interrupt status register ? byte 2 (address = 0x1109) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused change of ais-l defect condition interrupt status change of rdi-l defect condition interrupt status r/o r/o r/o r/o r/o r/o rur rur 0 0 0 0 0 0 1 0 2.3.1.4.2 how the receive sts-3 toh processor block clears the ais-l defect condition the receive sts-3 toh proc essor block will clear the ais-l defec t once it has received at least 5 consecutive sts-3 frames, in which bits 6, 7 and 8 (of t he k2 byte) are set to some value other than ?1, 1, 1?. once the receive sts-3 toh processor block clears the ais-l defect, it will notify the system of this fact by doing the following. ? it will set bit 0 (ais-l defect declared) within the re ceive sts-3 transport status register ? byte 1? to ?0? as illustrated below. receive sts-3 transport status register ? byte 1 (address = 0x1106) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused section trace message mismatch defect declared section trace message unstable defect declared ais_l defect declared r/o r/o r/o r /o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 ? it will generate the ?change of ais-l defect condition? interrupt by toggling the ?int*? output pin ?low?, and by setting bit 1 (change of ais-l defect condition in terrupt status), within the receive sts-3 transport interrupt status register ? byte 2? to ?1?, as illustrated below. receive sts-3 transport interrupt status register ? byte 2 (address = 0x1109) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused change of ais-l defect condition interrupt status change of rdi-l defect condition interrupt status r/o r/o r/o r/o r/o r/o rur rur
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 351 0 0 0 0 0 0 1 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 352 2.3.1.4.3 configuring the transmit sts-3 toh pro cessor block to automatically transmit the rdi-l indicator whenever the receive sts-3 toh processor block declares the ais-l defect condition the user can configure the transmit sts-3 toh proc essor block to automatica lly transmit the rdi-l indicator to the remote lte whenever (and for th e duration that) the corresponding receive sts-3 toh processor block declares t he ais-l defect condition. figure 85 presents an illustration of the transmit sts-3 toh processor block transmitting the rdi-l indicator, to the remote lte, whenever the correspo nding receive sts-3 toh processor block declares the ais-l defect condition. figure 85illustration of the transmit sts-3 to h processor block (within a given xrt94l33) transmitting the rdi-l indicator, to the remote lte whenever the corresponding receive sts-3 toh processor block declares the ais-l defect condition. the user can implement this configuration by setting bit 2 (transmit rdi-l upon ais-l) within the transmit sts-3 transport ? rdi-l control register, as depicted below. transmit sts-3 transport ? rdi-l control register (address = 0x1933) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused external rdi-l enable transmit rdi-l upon ais-l transmit rdi-l upon lof transmit rdi-l upon los r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 1 0 0 2.3.1.4.4 configuring the receive sts-3 toh process or block to automatically transmit the ais-p indicator in the down-stream direction (towards the receive sts-3c poh processor block) whenever it declar es the ais-l defect condition the user can configure the receive sts-3 toh proc essor block to automatically transmit the ais-p indicator, in the down-stream direction (towards t he corresponding receive sts-3c poh processor block) whenever (and for the duration that) it declares the ais-l defect condition. note: if the xrt94l33 is configured to operate in either th e ?1-channel sts-3 atm uni/ppp? mode, then the receive sts-3 toh processor block will trans mit the ais-p indicator to all three receive sonet poh processor blocks, in parallel, whenever it dec lares the ais-l defect condition. figure 86 presents an illustration of t he receive sts-3 toh processor bloc k transmitting the ais-p indicator, in the down-stream direction (towards the receive st s-3c poh processor block) whenever it declares the ais-l defect condition.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 353 figure 86 illustration of the receive sts-3 toh processor block tran smitting the ais-p indicator, in the down-stream direction (towards the receive sts-3c poh processor blocks) whenever it declares the ais-l defect condition transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3/12 toh processor block receive sts-3/12 toh processor block transmit sts-3/12 toh processor block transmit sts-3/12 toh processor block receive sts-3/12 poh processor block receive sts-3/12 poh processor block transmit sts-3/12 poh processor block transmit sts-3/12 poh processor block sts-3/12 telecom bus interface block sts-3/12 telecom bus interface block sts-3/12 pecl interface block sts-3/12 pecl interface block sts-3/12 cdr block sts-3/12 cdr block xrt95l34 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block ais-l ais-p the user can implement this configuration by setting bi ts 0 (auto ais), within the ?receive sts-3 transport ? auto ais control? register, to ?1? as depicted below. receive sts-3 transport ? auto ais control register (address = 0x1163) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 transmit ais-p (down- stream) upon section trace message unstable transmit ais-p (down- stream) upon section trace message mismatch transmit ais-p (down- stream) upon sf transmit ais-p (down- stream) upon sd transmit ais-p (down- stream) upon loss of optical carrier transmit ais-p (down- stream) upon lof transmit ais-p (down- stream) upon los auto ais r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 1 of course, if the receive sts-3 toh processor bloc k transmits the ais-p indicator towards the receive sts-3c poh processor block, then all of the following will happen. ? the receive sts-3c poh pr ocessor block will declare the ais-p defect condition.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 354 ? the corresponding receive atm cell processor block will declare the lcd (loss of cell delineation) defect condition. 2.3.1.5 rdi-l declaration and clearance criteria according to telecordia gr-253-core, a line terminating equipment must declare the rdi-l (line ? remote defect indicator) condition whenever it determine s that bits 6, 7 and 8 (w ithin the k2 byte) of the incoming sts-3c data-stream, are set the pattern [1 , 1, 0] for five consecutive sts-3c frames. figure 87 presents the illustration of th e ?rdi-l declaration/clearance? st ate machine diagram that is used by the receive sts-3 toh processor block within the xrt94l33. figure 87 illustration of the ?rdi-l declar ation/clearance? state machine diagram rdi-l defect is cleared rdi-l defect is cleared rdi-l defect is declared rdi-l defect is declared receive sts-3/sts-12 toh processor block receives five (5) consecutive frames in which bits 6, 7 and 8 (within the k2 byte) are set to the pattern [1, 1, 0] receive sts-3/sts-12 toh processor block receives five (5) consecutive frames in which bits 6, 7, and 8 (within the k2 byte) are not set to the pattern [1, 1, 0] 2.3.1.5.1 how the receive sts-3 toh processor block declares the rdi-l defect condition the receive sts-3c toh processor block is capable of declaring and clearing the rdi-l defect condition. if the receive sts-3 toh processor block receives at least five consecutive sts-3 frames, in which bits 6, 7 and 8 (within the k2 byte) are set to t he ?[1, 1, 0]? pattern, then it will dec lare the rdi-l defect condition. the receive sts-3 toh processor block will indicate that it is declaring the rdi-l defect condition by doing all of the following. ? it will set bit 7 (rdi-l defect declar ed) within the ?receive sts-3 transport status re gister ? byte 0? to ?1? as illustrated below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect dl d k1, k2 byte unstable defect dl d sf defect declared sd defect declared lof defect declared sef defect declared los defect declared
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 355 declared declared r/o r/o r/o r/o r /o r/o r/o r/o 1 0 0 0 0 0 0 0 ? it will generate the ?change in rdi-l defect condition? interrupt, by toggling the ?int*? output pin ?low?, and by setting bit 0 (change of rdi-l defect conditi on interrupt status) within the ?receive sts-3 transport interrupt status register ? byte 2? to ? 1? as illustrated below. receive sts-3 transport interrupt status register ? byte 2 (address = 0x1109) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused change of ais-l defect condition interrupt status change of rdi-l defect condition interrupt status r/o r/o r/o r/o r/o r/o rur rur 0 0 0 0 0 0 0 1 2.3.1.5.2 how the receive sts-3 toh processor block clears the rdi-l defect condition the receive sts-3 toh processor block will clear the rdi-l defect once it has received at least 5 consecutive sts-3 frames, in which bits 6, 7 and 8 (of t he k2 byte) are set to some value other than [1, 1, 0]. once the receive sts-3 toh processor bl ock clears the rdi-l defect, it will notify the system of this fact by doing the following. ? it will set bit 7 (rdi-l defect declar ed) within the receive sts-3 transpor t status register ? byte 0? to ?0? as illustrated below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect declared k1, k2 byte unstable defect declared sf defect declared sd defect declared lof defect declared sef defect declared los defect declared r/o r/o r/o r/o r /o r/o r/o r/o 0 0 0 0 0 0 0 0 ? it will generate the ?change in rdi-l defect condition? interrupt by toggling the ?int*? output pin ?low?, and by setting bit 0 (change of rdi-l defect conditi on interrupt status), within the ?receive sts-3 transport interrupt status register ? byte 2? to ?1?, as illustrated below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 356 receive sts-3 transport interrupt status register ? byte 2 (address = 0x1109) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused change of ais-l defect condition interrupt status change of rdi-l defect condition interrupt status r/o r/o r/o r/o r/o r/o rur rur 0 0 0 0 0 0 0 1 2.3.1.6 detecting an d flagging rei-l (line ? re mote error i ndicator) events the receive sts-3 toh processor block is capable of detecting the rei-l indicator, within the incoming sts-3 data-stream. as the receive sts-3 toh processor block receives a given sts-3 data-stream, it will monitor the contents within the m1 byte. the bit-form at of the m1 byte is presented below in figure 88. figure 88 bit format of the m1 byte b it 1 b it 2 b it 3 b it 4 b it 5 b it 6 b it 7 b it 8 b2 error count (rei-l) the role of the rei-l bit-fields was described in some detail, in section _. this section indicates that the remote terminal equipment will set the ?rei-l? value (withi n the m1 byte) to ?0? during ?un-erred? conditions. however, the remote terminal equipment will typically se t the ?rei-l? value to a value (ranging from ?1? to ?24?) during ?erred? conditions. if the receive sts-3 toh processor block receives an sts- 3 frame, that contains a ?non-zero? value of rei- l, then it will do the following. 15. it will generate the ?detection of rei-l error? interrupt. note: the receive sts-3 toh processor block will indicate this by, pulling the ?int*? output pin ?low? and by setting bit 5 (detection of rei-l error interrupt status), within the ?receive sts-3 transport ? interrupt status register ? byte 0? to ?1? as depicted below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 0 1 0 0 0 0 0 16. it will increment the ?receive sts-3 transport ? rei-l e rror count? registers note: these registers are actually 32-bit registers, which are located at direct address locations 0xna19 through 0xna1c. the bit-format of these registers is presented below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 357 receive sts-3 transport ? rei-l error count register ? byte 3 (address = 0x1118) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rei_l_error_count[31:24] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive sts-3 transport ? rei-l error count register ? byte 2 (address = 0x1119) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rei_l_error_count[23:16] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive sts-3 transport ? rei-l error count register ? byte 1 (address = 0x111a) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rei_l_error_count[15:8] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive sts-3 transport ? rei-l error count register ? byte 0 (address = 0x111b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rei_l_error_count[7:0] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 note: the receive sts-3 toh processor block will increment t hese registers either by the number of erred sts-3 frames (e.g., sts-3 frames with a non-zero rei-l value) detected, or by the value of the rei-l value, within the m1 byte of a given sts-3 frame; depending upon the user?s selection, as described below. 2.3.1.6.1 configuring the receive sts-3 toh pr ocessor block to increment the ?receive sts-3 transport ? rei-l error count? register on an ?rei-l value? basis the user can configure the receive sts-3 toh processor block to increment the ?receive sts-3 transport ? rei-l error count? register by the contents within the m1 byte, within each incoming sts-3 frame. therefore, in this mode, it is possible for the receiv e sts-3 toh processor block to increment this register by as much as the value ?24? for each sts-3 frame. the user can implement this configuration by setting bit 2 (rei-l error type) within the ?receive sts-3 transport ? control regi ster ? byte 0? to ?0?, as illustrated below. receive sts-3c transport control register ? byte 0 (address = 0x1103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused sf detect enable sd detect enable descramble disable sdh/sonet* rei-l error type b2 error type b1 error type r/o r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 358 2.3.1.6.2 configuring the receive sts-3 toh pr ocessor block to increment the ?receive sts-3 transport ? rei-l error count? register on a ?per sts-3 frame? basis. the user can also configure the receive sts-3 toh processor block to increment the ?receive sts-3 transport ? rei-l error count? register, by the value ?1? for each sts-3 frame that contains a ?non-zero? rei-l value. the user can implement this configuration by setting bit 2 (rei-l error type), within the ?receive sts-3 transport ? control regi ster ? byte 0? to ?1?, as illustrated below. receive sts-3 transport control register ? byte 0 (address = 0x1103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused sf detect enable sd detect enable descramble disable sdh/ sonet* rei-l error type b2 error type b1 error type r/o r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 1 0 0 2.3.1.6.3 reading out the contents of the ?receive sts-3 transport ? rei-l error count registers, during performance monitoring 2.3.1.7 receive section trace messa ges via the incoming j0 byte 2.3.1.8 handling/support of the incoming e1 byte 2.3.1.9 handling/support of the incoming f1 byte 2.3.1.10 handling/support of the incoming section dcc (d1, d2 and d3) bytes 2.3.1.11 section bip-8 (b1) byte verification the receive sts-3 toh processor block has the respon sibility for computing and verifying the section bip-8 (e.g., b1) byte within each incoming sts-3 frame. when the receive sts-3 toh processor block executes this function, it will do the following. ? it will read in the contents of a given ?newly received? sts-3 frame. ? it will compute the bip-8 value of this entire sts-3 frame. ? this resulting bip-8 value will be co mpared with the contents of the b1 byte, within the very next ?newly received? sts-3 frame. if the receive sts-3 toh processor block detects any b1 byte errors, then it will do the following. o it will generate the ?detection of b1 byte erro r? interrupt, by toggling the ?int*? output pin ?low? and by setting bit 3 (detection of b1 byte error interrupt status) within the ?receive sts-3 transport interrupt status? regi ster to ?1?, as indicated below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 1 0 0 0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 359 o it will increment the ?receive st s-3 transport b1 byte error co unt? registers. the ?receive sts-3 transport b1 error count? register is act ually a 32 bit register that resides at address locations = 0x1110 through 0x1113. the receive sts-3 toh proces sor block will increment these registers either by the number of erred sts-3 frames detected, or by the number of b1 bits that are detected to be in error (within a given sts-3 frame), depending upon user selection, as described below. 2.3.1.11.1 configuring the receive sts-3 toh pr ocessor block to increment the ?receive sts-3 transport b1 byte error count? registers on a ?per-frame? basis. the user can configure the receive sts-3 toh processor block to increment the ?receive sts-3 transport b1 byte error count? register, by the value ?1? for ea ch sts-3 frame that it det ermines to have at least one bit-error within the b1 byte. the user can accomplish this by setting bit 0 (b1 byte error type), within the ?receive sts-3 transport control register ? byte 0? to ?1?, as illustrated below. receive sts-3 transport control register ? byte 0 (address = 0x1103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused sf detect enable sd detect enable descramble disable sdh/sonet* rei-l error type b2 byte error type b1 byte error type r/o r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 1 2.3.1.11.2 configuring the receive sts-3 toh pr ocessor block to increment the ?receive sts-3 transport b1 error count? register on a ?per b1 bit error? basis. the user can configure the receive sts-3 toh processor block to increment the ?receive sts-3 transport b1 error count? register by the number of b1 bits, which are determined to be in error. therefore, in this mode, it is possible for the receive sts-3 toh processor block to increment this register by as much as the value of ?8? per sts-3 frame. the user can accomplish this by setting bit 0 (b1 by te error type) within the ?receive sts-3 transport control register ? byte 0? to ?0?, as illustrated below. receive sts-3 transport control register ? byte 0 (address = 0x1103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused sf detect enable sd detect enable descramble disable sdh/sonet* rei-l error type b2 byte error type b1 byte error type r/o r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.3.1.11.3 b1 byte performance monitoring 2.3.1.12 line bip-8 (b2) byte verification the receive sts-3 toh processor bloc k has the responsibility for comput ing and verifying the line bip-8 (e.g., b2) byte within each incoming sts-3 frame. when the receive sts-3 toh processor block executes this function, it will do the following. ? it will read in the contents of a given ?newly received? sts-3 frame. ? it will compute the bip-8 value over the loh (line overhead) and the envelope capacity, within this sts-3 frame.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 360 ? this resulting bip-8 value will be co mpared with the contents of the b2 byte, within the very next ?newly received? sts-3 frame. if the receive sts-3 toh processor block detects any b2 byte errors, then it will do the following. o it will generate the ?detection of b2 byte erro r? interrupt, by toggling the ?int*? output pin ?low? and by setting bit 4 (detection of b2 byte error interrupt status) within the ?receive sts-3 transport interrupt status? regi ster to ?1?, as indicated below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 0 0 1 0 0 0 0 o it will increment the ?receive st s-3 transport b2 byte error co unt? registers. the ?receive sts-3 transport b2 byte error count? register is actually a 32 bit register that resides at address locations 0x1114 through 0x1117. note: the receive sts-3 toh processor block will increment t hese registers either by the number of erred sts-3 frames detected, or by the number of b2 bits that are detected to be in error (within a given sts-3 frame), depending upon user selection, as described below. 2.3.1.12.1 configuring the receive sts-3 toh pr ocessor block to increment the ?receive sts-3 transport b2 error count? register on a ?per-frame? basis. the user can configure the receive sts-3 toh processor block to increment the ?receive sts-3 transport b2 byte error count? register, by the value ?1? for ea ch sts-3 frame that it determined to have at least one bit-error within the b2 bytes. the user can accomplish this by setting bit 1 (b2 erro r type), within the ?receive sts-3 transport control register ? byte 0? to ?1?, as illustrated below. receive sts-3 transport control register ? byte 0 (address = 0x1103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused sf detect enable sd detect enable descramble disable sdh/sonet* rei-l error type b2 error type b1 error type r/o r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 1 0 2.3.1.12.2 configuring the receive sts-3 toh pr ocessor block to increment the ?receive sts-3 transport b2 error count? register on a ?per b2 bit error? basis the user can configure the receive sts-3 toh processor block to increment the ?receive sts-3 transport b2 error count? register by the numbe r of ?b2 bits, which are determined to be in error. therefore, in this mode, it is possible for the receive sts-3 toh processor block to increment this register by as much as the value of ?24? for each sts-3 frame. the user can accomplish this by setting bit 1 (b2 er ror type) within the ?receive sts-3 transport control register ? byte 0? to ?0?, as illustrated below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 361 receive sts-3 transport control register ? byte 0 (address = 0x1103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused sf detect enable sd detect enable descramble disable sdh/sonet* rei-l error type b2 error type b1 error type r/o r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 the detection of b2 byte errors also plays a role in some of the other following functions. ? the transmission of the rei-l (line ? remote error indi cator) in the ?upstream? direction back out the to the remote terminal equipment. ? the declaration and clearance of the sd (signal degrade) and sf (signal fail) defect conditions. each of these items will be discussed in some detail in the next few sections. 2.3.1.12.3 b2 byte performance monitoring 2.3.1.12.4 transmission of rei-l in res ponse to detection of b2 byte errors 2.3.1.13 the sd (signal degrade) declaration and clearance criteria the receive sts-3 toh processor block is capable of declaring and clearing the sd defect condition. further, the receive sts-3 toh proces sor block register set permits the user to define both the ?sd defect declaration? and ?clearance? criteria. each receive sts-3 toh processor block contains an sd detector. the sd detect or accumulates b2 byte errors over a ?user-defined? monitoring period of time . if the number of b2 errors (accumulated over this ?user-defined? period of time) exceeds a user-defined ?s d declaration b2 byte error threshold?, then the sd detector will declare the ?sd? defect condition. similarly, if the sd defect is curr ently being declared, then t he ?sd detector? will continue to accumulate b2 byte errors over another ?user-defined? monitor period of time. if the number of b2 byte errors (accumulated over this ?user-defined? period of time) is less than a ?user-defined sd defect clearance b2 byte error? threshold, then the sd detector w ill clear the sd defect condition. it should be noted that the receive sts-3 toh processo r block (within the xrt94l33) permits the user to independently specify the ?sd defect declaration b2 by te error? threshold and the ?sd defect clearance b2 byte error? threshold. as a consequence, the user ca n implement some sort of hysteresis within the sd defect declaration or cl earance thresholds. in orde r to further enhance the user?s ability to specify the sd defect declaration and clearance thresholds, the user can also independently specify monitoring times that are to be used in order to declare or clear the sd defect condition. 2.3.1.13.1 the types of b2 byte errors prior to describing the behavior of the sd detector, it is imperative to review the types of b2 byte errors that can be accumulated for the sake of sd defect declarat ion or clearance. the receive sts-3 toh processor block can be configured to tally b2 byte errors in one of two-different manners. ? on a ?per-bit? basis ? on a ?per-frame? basis if the user configures the receive sts- 3 toh processor block to ?tally? b2 byte errors on a ?per-bit? basis, then it will declare an error for each bit (within the incoming b2 byte) that is determined to be in error. in this case, the receive sts-3 toh processor block can declare as many as 24 b2 byte errors, per sts-3 frame (e.g., when all 8 bit, within each of the 3 incoming b2 bytes, are in error).
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 362 conversely, if the user configures the receive sts-3 toh processor block to ?tally? b2 errors on a ?per- frame? basis, then it will declare a single b2 byte error, anytime at least one bit, within the 3 or 12 b2 bytes (within a given incoming sts-3 frame) is determined to be in error. in this case, the receive sts-3 toh processor block will at most declare one b2 byte error, per sts-3 frame. the user can configure the receive sts-3 toh processor block to ?tally? b2 errors on a ?per-bit? basis, by setting bit 1 (b2 byte error type), within the ?receive st s-3 transport control register ? byte 0? to ?0?, as depicted below. receive sts-3 transport control register ? byte 0 (address = 0x1103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused sf defect detect enable sd defect detect enable descramble disable sdh/sonet* rei-l error type b2 byte error type b1 byte error type r/o r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 likewise, the user can configure the receive sts-3 toh processor block to ?tally? b2 byte errors on a ?per- frame? basis, by setting bit 1 (b2 byte error type) to ?1?, as depicted below. receive sts-3 transport control register ? byte 0 (address = 0x1103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused sf defect detect enable sd defect detect enable descramble disable sdh/sonet* rei-l error type b2 byte error type b1 byte error type r/o r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 1 0 this configuration option, on how the receive sts-3 toh processor block ?tallies? b2 byte errors impacts the following functions. ? the sd defect declarat ion and clearance criteria ? the sf defect declaration and clearance criteria ? the amount by which the receive sts-3 toh pr ocessor block will increment the ?receive sts-3 transport ? b2 byte error count? registers. 2.3.1.13.2 the sd (signal degrade) defect declaration criteria the xrt94l33 permits the user to specify three parame ters to define the sd defe ct declaration criteria. ? the minimum number of b2 byte errors (e.g., a b2 byte error-threshold) accumulated over a given ?sd set interval? time period. from this poi nt on, this particular ?b2 byte error? threshold will be referred to as the ?sd defect declare b2 byte error? threshold. ? the length (in terms of sts-3 frame periods) of this ?sd set interval? monitoring time period for the sd detector to tally b2 byte errors. from this point on, this particular ?user-defined? monitoring time period will be referred to as the ?sd defe ct declare monitor? time. ? the maximum number of b2 byte errors that will be counted within a sub-internal period towards the declaration of the sd defect condition. from this poi nt on, this maximum number of b2 byte errors will be referred to as the ?sd detect b2 error burst limit?. once the user defines these parame ters, then the receive sts-3 toh pr ocessor block will begin to count the cumulative number of b2 errors that it detects within a ?sliding window? of time. the length of this ?sliding window of time? is dictated by the ?s d defect declare monitor? time period.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 363 as long as the receive sts-3 toh processor block does not detect the ?sd defect declare b2 byte error- threshold? number of b2 byte errors, within this ?s d defect declare monitor? time period, then it will not declare the sd defect condition. conversely, if the receive sts-3 toh processor block detects at least the ?sd defect declare b2 error threshold? number of b2 by te errors, within the ?sd defect declare monitor time period, then it will declare the sd defect condition. figure 89 presents an illustration of t he sd detector accumulating b2 byte errors over a ?monitoring? time period. figure 89 a conceptual illustration of the sd detector accumulating b2 byte errors over a ?monitoring? time period s pecifying the ?sd d efect d eclare b2 b yte e rror ? t hreshold the user can specify the ?sd defect declare b2 byte e rror threshold? by writing the appropriate value into the ?receive sts-3 transport ? receive sd set threshol d ? byte 1 and byte 0? registers, as depicted below. receive sts-3 transport ? receive sd set threshold ? byte 1 (address = 0x1142) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_threshold[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3 transport ? receive sd set threshold ? byte 0 (address = 0x1143) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_threshold[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 notes: the ?receive sts-3 transport ? receive sd set threshold ? byte 1 and byte 0? registers permits the user to write in a 16-bit expression for the ?sd defect declare b2 byte error threshold?. the ?default? value for the ?b2 byte error threshold? is 0xffff. s pecifying the length of the ?sd d efect d eclare m onitor t ime ? p eriod likewise, the user can specify the length of the ?sd defect declare monitor time? period by writing the appropriate value into the ?receive sts-3 transport ? receive sd set monitor interval ? byte 2, 1 and 0? registers, as depicted below. receive sts-3 transport ? receive sd set monitor interval ? byte 2 (address = 0x113d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 364 receive sts-3 transport ? receive sd set monitor interval ? byte 1 (address = 0x113e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sd set monitor interval ? byte 0 (address = 0x113f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 note: the ?receive sts-3 transport ? receive sd set monitor in terval ? byte 2, byte 1 and byte 0? registers permit the user to write in a 24-bit expression for the ?sd defe ct declare monitor time? period. the number that is written into these registers represents the duration of t he ?sd defect declare monitor time? period, in terms of 1 millisecond units. example of defining the sd declaration criteria suppose that the user writes in the value ?0x000f? into the ?receive sts-3 transport ? receive sd set threshold? registers; as depicted below. receive sts-3 transport ? receive sd set threshold ? byte 1 (address = 0x1142) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_threshold[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sd set threshold ? byte 0 (address = 0x1143) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_threshold[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 1 1 1 1 additionally, now suppose that the user writes in the value ?0x000010? into the ?receive sts-3 transport ? receive sd set monitor interval ? registers; as depicted below. receive sts-3 transport ? receive sd set monitor interval ? byte 2 (address = 0x113d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 365 receive sts-3 transport ? receive sd set monitor interval ? byte 1 (address = 0x113e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sd set monitor interval ? byte 0 (address = 0x113f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 0 once the user has executed these two steps, then the ?sd declaration criteria? will be as summarized below. ? the ?sd defect declare b2 byte error? threshold = 0x0f (or 15) b2 errors. ? the sd defect declare monitor time period = 0x10 (or 16ms) hence, the receive sts-3 toh processor block will accumulate b2 byte erro rs over a 16ms period. at this point, the receive sts-3 toh processor block will proceed to count b2 byte errors. based upon the ?above-mentioned? configuration selections, if the rece ive sts-3 toh processor block detects 15 or more b2 byte errors, within a given 16ms period then it will dec lare the sd defect condition. conversely, if the sd detector detects less than 15 b2 byte errors within this 16ms period, then it will not declare the sd defect condition. error burst filtering of b2 byte errors for declaration of the sd defect condition in some applications it may be necessary to insure t hat the sd defect condition is declared based upon the long-term performance characteristics of a given inco ming sts-3 signal, and is not induced by a single ?burst of errors? occurring within this sts-3 signal. an example of where this feature might be useful is whenever one implements aps (a utomatic protection switching) in re sponse to the declaration of the sd defect condition. in this situation, it is undesir able to permit a single error-burst (which occurs in an ?otherwise? error-free sts-3 signal) to result in aps switching to a redundant sts-3 signal, and thereby temporarily (and needlessly) disrupting atm or ppp traffic across this aps event. as a consequence, the sd detector within the receiv e sts-3 toh processor block contains an ?error-burst? filter which is set by selecting the appropria te ?sd defect b2 byte error burst? limit. setting the ?sd defect b2 byte error burst? limit as mentioned above, the user can spec ify the ?sd defect declare monitor? time interval (e.g., the amount of time that the sd detector will accu mulate b2 byte errors, when determin ing whether to declare the sd defect or not). this particular ?sd defect declare monitor time ? interval is sub-divided in to eight (8) ?sub-interval? periods. the ?error burst filter? permits the user to spec ify an upper limit to the number of b2 byte errors that the sd detector can accumulate during a given ?sub-in terval? period; when determining whether or not to declare the sd defect condition. the user can set the ?err or burst? filter by writing the appropriate value into the ?receive sts-3 transport ? receive sd burst error tolerance ? byte 1 & byte 0? registers as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 366 receive sts-3 transport ? receive sd burst error tolerance ? byte 1 (address = 0x1152) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_burst_tolerance[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3 transport ? receive sd burst error tolerance ? byte 0 (address = 0x1153) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_burst_tolerance[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 note: the default value for the contents within the ?receive sts-3 transport ? receive sd burst error tolerance? register is 0xffff. this means that the sd detector c an receive (and tally) up to 65,535 b2 byte errors within a given sub-interval period. beyond this point, the sd de tector will cease to tally anymore b2 byte errors during this ?sub-interval? period. the value that is written into thes e registers dictates the maximum numbe r of b2 byte errors that the sd detector will accumulate over a ?sub-interval? period , when checking to determine if it should declare the sd defect condition. example of using the sd error burst filter let?s suppose that a customer wish es to configure the sd detector to declare the sd defect condition whenever the bit error rate (ber) within an incoming sts-12 signal exceeds 1x10-9. further, let us assume that the customer wants to continuously check for a ber of 1x10-9 over a ?sliding monitor? window of 167 seconds. the user must then execute the following steps in order to implement this configuration setting. step 1 ? setting the ?sd defect declare monitor? interval to 167 seconds since 167 seconds corresponds to 167,000ms, then we need to write in the value 167,000 or 0x028c58 into the ?receive sts-3 transport ? receive sd set monitor interval? register, as depicted below. receive sts-3 transport ? receive sd set monitor interval ? byte 2 (address = 0x113d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 1 0 receive sts-3 transport ? receive sd set monitor interval ? byte 1 (address = 0x113e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 1 0 0 0 1 1 0 0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 367 receive sts-3 transport ? receive sd set monitor interval ? byte 0 (address = 0x113f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 1 0 1 1 0 0 0 step 2 ? setting the ?sd defect declare b2 error threshold? to 1x10-9 within 167 seconds, ther e will be [167 seconds ? 622.08mbits/second] = 103.9gb of data that will have been transmitted via an sts-12 data-stream. as a consequence, if the ber is 1x10 -9, then there will be [167 seconds ? 622.08mbits/second ? 1x10-9 errors/bits] = 103.9 erred bits within a 167 second period. as a consequence, we need to write the value 104 (or 0x0068) into the ?receive sts-3 transport ? receive sd set threshold? registers as depicted below. receive sts-3 transport ? receive sd set threshold ? byte 1 (address = 0x1142) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_threshold[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sd set threshold ? byte 0 (address = 0x1143) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_set_threshold[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 1 1 0 1 0 0 0 based upon the configuration settings that were impl emented within steps 1 and 2, the sd detector will declare the sd defect condition anytime it detects 104 b2 byte errors within a given 167 second ?sd defect declare monitor time? period. now, let?s suppose that this incoming sts-12 signal is ?error-free?, and that the sd detector is currently not declaring the sd defect condition; and that it has curr ently talled 0 b2 byte errors during the current ?sd defect declaring monitor time? period. now, let?s further suppose that a burst of errors (lasting 1us) occurs within this sts-12 data-stream. we will also presume that the ?timing? of th is ?error-burst? event is such that it straddles two sts-12 frames. if the receive sts-12 toh processor block is configured to accumulate b2 byte errors in a ?per-bit? manner (please see section _ for a definition of ?per-bit man ner?) then the sd detector can accumulate and tally as much as 96 b2 byte errors/sts-12 x 2 sts-12 frames =) 192 b2 byte errors. in this example, this single burst of errors within the in coming sts-12 signal will cause the sd detect or to declare the sd defect (since it has accumulated 192 b2 byte errors within a given 1 67 second ?sd defect declare monitor time? period). occurrence whenever the receive sts-3 toh processor block declares the sd defect condition anytime the receive sts-3 toh processor block decla res the sd defect condition, then it will do the following. ? it will generate the ?change of sd defect condition? interrupt
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 368 note: the receive sts-3 toh processor block will indicate that it is generating this interrupt by toggling the ?int*? output pin ?low? and by setting the ?change of sd defect condition interrupt status? bit to ?1?, as depicted below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 1 0 0 0 0 0 0 ? it will set bit 3 (sd defect declared), within the ?rec eive sts-3 transport status register ? byte 0? to ?1?, as depicted below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect declared k1, k2 byte unstable defect declared sf defect declared sd defect declared lof defect declared sef defect declared los defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 1 0 0 0 2.3.1.13.3 the sd (signal degrade) defect clearance criteria the xrt94l33 permits the user to specify the following two parameters to define the sd defect clearance criteria. ? the maximum number of b2 errors (e.g., a b2 byte er ror-threshold) accumulated over a given ?sd defect clear monitor? time period. ? the length of this ?sd defect clear monitor? time period. once the user defines these parame ters, then the receive sts-3 toh pr ocessor block will begin to count the cumulative number of b2 byte errors that it detects within a ?sliding window? of time. the length of this ?sliding window of time? is dictated by the user- defined ?sd defect clear monitor? time period. if the receive sts-3 toh processor bloc k is currently declaring the sd defect condition, and if continues to detects more than the ?sd defect clear b2 error threshol d? number of b2 errors; within the ?sd defect clear monitor? of time, then it will not clear the sd defe ct condition. conversely, if the receive sts-3 toh processor block detects less than the ?sd defect clear b2 byte error threshold? number of b2 byte errors, within the ?sd defect clear monitor? period of time, then it will clear the sd defect condition. specifying the ?b2 byte error threshold? for clearing the sd defect condition the user can specify the ?sd defect clear b2 byte erro r threshold? by writing the appropriate value into the ?receive sts-3 transport ? receive sd clear threshol d ? byte 1 and byte 0? registers, as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 369 receive sts-3 transport ? receive sd clear threshold ? byte 1 (address = 0x1146) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_clear_threshold[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3 transport ? receive sd clear threshold ? byte 0 (address = 0x1147) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_clear_threshold[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 notes: the ?receive sts-3 transport ? receive sd clear threshold ? by te 1 and byte 0? registers permits the user to write in a 16-bit expression for the ?sd defect clear b2 error threshold?. the ?default? value for the ?sd defect clear b2 error threshold? is ?0xffff?. specifying the length of the ?sd defect clear monitor? period of time likewise, the user can also specify the ?sd defect clear interval? period by writing the appropriate value into the ?receive sts-3 transport ? receive sd clear monitor interval ? byte 2, 1, and 0? registers, as depicted below. receive sts-3 transport ? receive sd clear monitor interval ? byte 2 (address = 0x1159) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_clear_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3 transport ? receive sd clear monitor interval ? byte 1 (address = 0x115a) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_clear_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3 transport ? receive sd clear monitor interval ? byte 0 (address = 0x115b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_clear_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 note: the ?receive sts-3 transport ? receive sd clear monitor in terval ? byte 2, byte 1 and byte 0? registers permit the user to write in a 24-bit expression for the length of the ?sd defect clear monitor period?. the number that is written into these registers repres ents the duration of the ?s d clear interval? period, in terms one millisecond units.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 370 example of defining the sd defect clearance criteria suppose that the user writes in the value ?0x0008? in to the ?receive sts-3 transport ? receive sd defect clear threshold? registers; as depicted below. receive sts-3 transport ? receive sd clear threshold ? byte 1 (address = 0x1146) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_clear_threshold[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sd clear threshold ? byte 0 (address = 0x1147) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_clear_threshold[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 1 0 0 0 additionally, now suppose that the user writes in the value ?0x000100? into the ?receive sts-3 transport ? receive sd clear monitor interval ? registers; as depicted below. receive sts-3 transport ? receive sd clear monitor interval ? byte 2 (address = 0x1159) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_clear_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sd clear monitor interval ? byte 1 (address = 0x115a) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_clear_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 1 receive sts-3 transport ? receive sd clear monitor interval ? byte 0 (address = 0x115b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sd_clear_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 once the user has executed these two steps, then t he ?sd defect clearance criteria? will now be as summarized below. ? the sd defect clear b2 byte error thre shold = 0x08 (or 8) b2 byte errors ? the sd defect clear monitor period = 0x100 (or 256ms) hence, in order to determine whether to clear the sd defect condition or not, the sd detector (within the receive sts-3 toh processor bl ock) will tally b2 byte erro rs over this 256ms period.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 371 at this point, the receive sts-3 toh processor block will proceed to count b2 byte errors. if the receive sts-3 toh processor block is currently declaring the sd defect condition; it will now clear the sd defect condition if it detects less than 8 b2 by te errors, within a given 256ms period. occurrences whenever the receive sts-3 toh processor block clears the sd defect condition anytime the receive sts-3 toh proces sor block clears the sd defect cond ition, then it will do the following. ? it will generate the ?change of sd defect condition? interrupt note: the receive sts-3 toh processor block will indicate that it is generating this interrupt by toggling the ?int*? output pin ?low? and be setting the ?change of sd defect condition interrupt status? bit to ?1?, as depicted below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf defect condition interrupt status change of sd defect condition interrupt status detection of rei-l error interrupt status detection of b2 byte error interrupt status detection of b1 byte error interrupt status change of lof defect condition interrupt status change of sef defect condition interrupt status change of los defect condition interrupt status rur rur rur rur rur rur rur rur 0 1 0 0 0 0 0 0 ? it will set bit 3 (sd defect declared) within the ?receive sts-3 transport st atus register ? byte 0? to ?0?, as depicted below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l defect declared s1 byte unstable defect declared k1, k2 byte unstable defect declared sf defect declared sd defect declared lof defect declared sef defect declared los defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 2.3.1.14 sf declaratio n and clearance criteria the receive sts-3 toh processor block is capable of decl aring and clearing the sf condition. further, the receive sts-3c toh processor block register set per mits the user to define the ?sf declaration? and ?clearance? criteria. the receive sts-3 toh processor block actually consists of two different ?sf? detectors. ? the ?interval? sf detector ? the ?burst? sf detector the ?interval? sf detector accumulates b2 errors over a long ?user-defined? period of time. if the number of b2 errors (accumulated over this ?user-defined? period of time) exceeds a user-def ined ?threshold?, then the ?interval? sf detector will declare an ?sf? condition. the ?burst? sd detector functions similarly to that of the ?interval? sf detector, in that it also accumulates b2 errors over a ?user-defined? period of time. further, the ?burst? sf detector will declare the sf condition if the number of b2 errors (accumulated over this ?user-defi ned? period of time) exceeds a ?user-defined? threshold, then the ?burst? sd detector will declare an ?sf condition?. there are two main differences between the ?inter val? sf detector and the ?burst? sf detectors.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 372 1. the ?interval? sf detector will accumulate b2 er rors over a much greater amount of time (e.g., 8 times greater) than that of the ?burst? sf detector; when det ermine whether to declare/clear the sf condition, or not. 2. the ?interval? sf detector per mits a ?user-defined? hysteresis betwe en the conditions required to declare and clear the sf condition. the ?burst? sf detector per mits no hysteresis between the conditions required to declare and clear the sf condition. 2.3.1.14.1 the definition of b2 errors the receive sts-3 toh processor block can be configur ed to tally b2 errors in one of two-different manners. ? on a ?per-bit? basis ? on a ?per-frame? basis if the user configures the receive sts-3 toh processor bl ock to ?tally? b2 errors on a ?per-bit? basis, then it will declare an error for each bit (within the incoming b2 by te) that is determined to be in error. in this case, the receive sts-3 toh processor block can declare as many as 8 b2 errors, per sts-3 frame (e.g., when all 8 bit, within the incoming b2 byte, are in error). conversely, if the user configures the receive sts-3 toh processor block to ?tally? b2 errors on a ?per- frame? basis, then it will declare a single b2 error, anyt ime an incoming b2 byte is determined to be in error. in this case, the receive sts-3 toh processor block will only declare as many as 1 b2 error, per sts-3 frame. the user can configure the receive sts-3 toh processor block to ?tally? b2 errors on a ?per-bit? basis, by setting bit 1 (b2 error type), within the ?receive sts-3 transport control register ? byte 0? to ?0?, as depicted below. receive sts-3 transport control register ? byte 0 (address = 0x1103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused sf detect enable sd detect enable descramble disable sdh/sonet* rei-l error type b2 error type b1 error type r/o r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 likewise, the user can configure the receive sts-3 toh processor block to ?tally? b2 errors on a ?per-frame? basis, by setting bit 1 (b2 error type) to ?1?, as depicted below. receive sts-3 transport control register ? byte 0 (address = 0x1103) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused sf detect enable sd detect enable descramble disable sdh/ sonet* rei-l error type b2 error type b1 error type r/o r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 1 0 this configuration option, on how t he receive sts-3 toh processor block ?tallies? b2 errors impacts the following functions. ? the sf declaration and clearance criteria ? the sd declaration and clearance criteria ? the values that the corresponding transmit sts-3 toh processor block, will transmit to the remote terminal, via the rei-l bit-fields (within the m0 byte).
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 373 ? the amount by which the receive sts-3 toh pr ocessor block will increment the ?receive sts-3 transport ? b2 error count? registers. the relationship between the ?overall? sf conditi on, and the states of the ?interval? and ?burst? detectors the ?sf condition? (as declared and cleared by the receive sts-3 toh pr ocessor block) is the ?logical or? of the ?sf declaration? state of t he ?interval? and ?burst? sf detector. in other words, the receive sts-3 toh processor block w ill declare the sf condition, if either the ?interval? or the ?burst? sf detector are curr ently declaring the ?sf condition?. the operation of the ?interval? and ?burst? sf detectors are both described in detail below. 2.3.1.14.2 the sf (signal fail) defect declaration criteria in this case, the user specifies three parame ters to define the sf declaration criteria. ? the minimum number of b2 errors (e.g., a b2 error-threshold) accumulated over a given ?sf set interval? time period. ? the length (in terms of sonet frame periods ) of this ?sf set interval? time period. once the user defines these parame ters, then the receive sts-3 toh pr ocessor block will begin to count the cumulative number of b2 errors that it detects within a ?sliding window? of time. the length of this ?sliding window of time? is dictated by the user -defined ?sf set interval? time period. as long as the receive sts-3 toh processor block doe s not detect the ?b2 error-threshold? number of b2 errors, within this ?sf set interval? of time, then it will not declare the sf condition. conversely, if the receive sts-3c toh processor block detects at least the ?b2 error threshold? number of b2 errors, within the ?sf set interval? of time, then it will declare the sf condition. s pecifying the ?b2 e rror t hreshold ? for d eclaring sf the user can specify the ?b2 error threshold? by wr iting the appropriate value into the ?receive sts-3 transport ? receive sf set threshold ? byte 1 and byte 0? registers, as depicted below. receive sts-3 transport ? receive sf set threshold ? byte 1 (address = 0x1136) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_threshold[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3 transport ? receive sf set threshold ? byte 0 (address = 0x1137) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_threshold[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 notes: the ?receive sts-3 transport ? receive sf set threshold ? byte 1 and byte 0? registers permits the user to write in a 16-bit expression for the ?b2 error threshold?. the ?default? value for the ?b2 error threshold? is 0xffff. s pecifying the ?sf s et i nterval ? of t ime likewise, the user can specify the ?sf set interval? perio d by writing the appropriate value into the ?receive sts-3 transport ? receive sf set monitor interval ? byte 2, 1 and 0? registers, as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 374 receive sts-3 transport ? receive sf set monitor interval ? byte 2 (address = 0x1131) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf set monitor interval ? byte 1 (address = 0x1132) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf set monitor interval ? byte 0 (address = 0x1133) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 notes: the ?receive sts-3 transport ? receive sf set monitor interval ? byte 2, byte 1 and byte 0? registers permit the user to write in a 24-bit expression for the ?sf set interval?. the number that is written into these registers represents the duration of the ?sf set interval? peri od, in terms of sonet frame periods. the actual length of time t hat the receive sts-3 toh processor block will us e (to accumulate b2 errors) to declare the sf condition is eight times the value written into these registers. e xample of d efining the sf d eclaration c riteria ? sf i nterval d etector suppose that the user writes in the value ?0x000f? into the ?receive sts-3 transport ? receive sf set threshold? registers; as depicted below. receive sts-3 transport ? receive sf set threshold ? byte 1 (address = 0x1136) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_threshold[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf set threshold ? byte 0 (address = 0x1137) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_threshold[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 1 1 1 1 additionally, now suppose that the user writes in the value ?0x000010? into the ?receive sts-3 transport ? receive sf set monitor interval? registers; as depicted below. receive sts-3 transport ? receive sf set monitor interval ? byte 2 (address = 0x1131)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 375 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf set monitor interval ? byte 1 (address = 0x1132) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf set monitor interval ? byte 0 (address = 0x1133) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 0 once the user has executed these two steps, then the ?sf declaration criteria? will be as summarized below. ? b2 error threshold = 0x0f (or 15) b2 errors. ? sf set interval = 0x10 (or 16 sonet frame periods) hence, the receive sts-3c toh processor block will accumulate b2 errors over 128 (e.g., 8 * 16) sonet frame periods. at this point, the receive sts-3 toh processor block will proceed to coun t b2 errors. anytime the receive sts-3 toh processor block detects 15 or more b2 errors, within a 16ms period (e.g., 128 sonet frame periods); then it will declare the sf condition. occurrence whenever the receive sts-3 toh processor block declares the sf condition anytime the receive sts-3 toh processor block declar es the sf condition, then it will do the following. ? it will generate the ?change of sf condition? interrupt note: the receive sts-3 toh processor block will indicate that it is generating this interrupt by toggling the ?int*? output pin ?low? and by setting the ?change of sf conditi on interrupt status? bit to ?1?, as depicted below. receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf condition interrupt status change of sd condition interrupt status rei-l error interrupt status b2 error interrupt status b1 error interrupt status change of lof condition interrupt status sef interrupt status change of los condition interrupt status rur rur rur rur rur rur rur rur 1 0 0 0 0 0 0 0 ? it will set bit 4 (sf detected), within the ?receive sts-3c transport status register ? byte 0? to ?1?, as depicted below. receive sts-3 transport status register ? byte 0 (address = 0x1107)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 376 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l declared s1 unstable aps unstable sf detected sd detected lof defect detected sef defect declared los defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 1 0 0 0 0 2.3.1.14.3 the sf (signal fail) defect clearance criteria in this case, the user specifies two parameters to define the sf clearance criteria. ? the maximum number of b2 errors (e.g., a b2 e rror-threshold) accumulated over a given ?sf clear interval? time period. ? the length (in terms of sonet frame periods ) of this ?sf clear interval? time period. once the user defines these parameters, then the receive sts-3c toh processor block will begin to count the cumulative number of b2 errors that it detects within a ?sliding window? of time. the length of this ?sliding window of time? is dictated by the user -defined ?sf clear interval? time period. if the receive sts-3c toh processor block is current ly declaring the sf condition, and if continues to detects more than the ?b2 error threshold? number of b2 errors; within the ?sf clear interval? of time, then it will not clear the sf condition. conversely, if the receive sts-3c toh processo r block detects less than the ?b2 error threshold? number of b2 errors, within t he ?sf clear interval? of time, then it will clear the sf condition. specifying the ?b2 error threshold? for clearing sf the user can specify the ?b2 error threshold? by writ ing the appropriate value into the ?receive sts-3c transport ? receive sf clear threshold ? byte 1 and byte 0? registers, as depicted below. receive sts-3 transport ? receive sf clear threshold ? byte 1 (address = 0x113a) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_threshold[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3 transport ? receive sf clear threshold ? byte 0 (address = 0x113b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_threshold[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 notes: the ?receive sts-3 transport ? receive sf clear threshold ? by te 1 and byte 0? registers permits the user to write in a 16-bit expression for the ?b2 error threshold?. the ?default? value for the ?b2 error threshold? is ?0xffff?.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 377 specifying the ?sf clear interval? of time likewise, the user can specify the ?sf clear interval? per iod by writing the appropriate value into the ?receive sts-3 transport ? receive sf clear monitor interval ? byte 2, 1, and 0? registers, as depicted below. receive sts-3 transport ? receive sf clear monitor interval ? byte 2 (address = 0x115d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3 transport ? receive sf clear monitor interval ? byte 1 (address = 0x115e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3 transport ? receive sf clear monitor interval ? byte 0 (address = 0x115f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 notes: the ?receive sts-3 transport ? receive sf clear monitor interv al ? byte 2, byte 1 and byte 0? registers permit the user to write in a 24-bit expression for the ?sf clear interval?. the number that is written into these registers represents the duration of the ?sf clear interval? period , in terms of sonet frame periods. the actual length of time that the receive sts-3 toh processor block will use (to accumulate b2 errors) to declare the sf condition is eight times the value written into these registers. example of defining the sf clearance criteria suppose that the user writes in the value ?0x0008? in to the ?receive sts-3c transport ? receive sf clear threshold? registers; as depicted below. receive sts-3 transport ? receive sf clear threshold ? byte 1 (address = 0x113a) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_threshold[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf clear threshold ? byte 0 (address = 0x113b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_threshold[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 1 0 0 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 378 additionally, now suppose that the user writes in the value ?0x000100? into the ?receive sts-3 transport ? receive sf clear monitor interval? registers; as depicted below. receive sts-3 transport ? receive sf clear monitor interval ? byte 2 (address = 0x115d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf clear monitor interval ? byte 1 (address = 0x115e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 1 receive sts-3 transport ? receive sf clear monitor interval ? byte 0 (address = 0x115f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 once the user has executed these two steps, then the ?sf clearance criteria? will be as summarized below. ? b2 error threshold = 0x08 (or 8) b2 errors ? sf clear interval = 0x100 (or 256 sonet frame periods) hence, the receive sts-3 toh processor block will ac cumulate b2 errors over 2048 (e.g. 8 * 256) sonet frame periods. at this point, the receive sts-3 toh processor block will proc eed to count b2 errors. if the receive sts-3 toh processor block is currently declaring the sf condition; it will now clear the sf condition if it detects less than 8 b2 errors, within a 256ms period (e.g., 2048 sonet frame periods); then it will clear the sf condition. occurrences whenever the receive sts-3 toh processor block clears the sf condition anytime the receive sts-3 toh processor block clear s the sf condition, then it will do the following. it will generate the ?change of sf condition? interrupt note: the receive sts-3 toh processor block will indicate that it is generating this interrupt by toggling the ?int*? output pin ?low? and be setting the ?change of sf conditi on interrupt status? bit to ?1?, as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 379 receive sts-3 transport interrupt status register ? byte 0 (address = 0x110b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 change of sf condition interrupt status change of sd condition interrupt status rei-l error interrupt status b2 error interrupt status b1 error interrupt status change of lof condition interrupt status sef interrupt status change of los condition interrupt status rur rur rur rur rur rur rur rur 1 0 0 0 0 0 0 0 ? it will set bit 4 (sf detected) with in the ?receive sts-3 tr ansport status register ? byte 0? to ?0?, as depicted below. receive sts-3 transport status register ? byte 0 (address = 0x1107) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rdi-l declared s1 unstable aps unstable sf detected sd detected lof defect detected sef defect declared los defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 sf declaration criteria ? per the ?burst? sf detector in this case, the user specifies two parame ters to define the sf declaration criteria. ? the minimum number of b2 errors (e.g., a b2 error-threshold) accumulated over a given ?sf set interval? time period. ? the length (in terms of sonet frame periods ) of this ?sf set interval? time period. once the user defines these parame ters, then the receive sts-3 toh pr ocessor block will begin to count the cumulative number of b2 errors that it detects within a ?sliding window? of time. the length of this ?sliding window of time? is dictated by the user -defined ?sf set interval? time period. as long as the receive sts-3 toh processor block does not detects the ?b2 error threshold? number of b2 errors, within this ?sf set interval? of time, then it will not declare the sf condition. conversely, if the receive sts-3 toh processor block dete cts at least the ?b2 error threshold? number of b2 errors, within the ?sf set interval? of time, then it will declare the sf condition. specifying the ?b2 error threshold? for declaring sf the user can specify the ?b2 error threshold? by wr iting the appropriate value into the ?receive sts-3 transport ? receive sf burst error tolerance ? byte 1 and byte 0? registers, as depicted below. receive sts-3 transport ? receive sf burst error tolerance ? byte 1 (address = 0x1156) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_burst_tolerance[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 380 receive sts-3 transport ? receive sf burst error tolerance ? byte 0 (address = 0x1157) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_burst_tolerance[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 notes: the ?receive sts-3 transport ? receive sf burst error tolerance ? byte 1 and byte 0? registers permit the user to write in a 16-bit expression for the ?b2 error threshold? for the ?sf burst detector?. the ?default? value for the ?b2 error threshold? is 0xffff. s pecifying the ?sf s et i nterval ? of t ime likewise, the user can specify the ?sf set interval? perio d by writing the appropriate value into the ?receive sts-3 transport ? receive sf set monitor interval ? byte 2, 1, and 0? registers, as depicted below. receive sts-3 transport ? receive sf set monitor interval ? byte 2 (address = 0x1131) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf set monitor interval ? byte 1 (address = 0x1132) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf set monitor interval ? byte 0 (address = 0x1133) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 notes: the ?receive sts-3 transport ? receive sf set monitor interval ? byte 2, byte 1 and byte 0? registers permit the user to write in a 24-bit expression for the ?sf set interval?. the number that is written into these registers represents the duration of the ?sf set interval? peri od, in terms of sonet frame periods. the actual length of time t hat the receive sts-3 toh processor block will us e (to accumulate b2 errors) to declare the sf condition is value written into these registers. e xample of d efining the sf d eclaration c riteria ? sf b urst d etector suppose that the user writes in the value ?0x000f? in to the ?receive sts-3 transport ? receive sf burst error tolerance? registers; as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 381 receive sts-3 transport ? receive sf burst error tolerance ? byte 1 (address = 0x1156) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_burst_tolerance[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf burst error tolerance ? byte 0 (address = 0x1157) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_burst_tolerance[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 1 1 1 1 additionally, now suppose that the user writes in the value ?0x000010? into the ?receive sts-3 transport ? receive sf set monitor interval? register, as depicted below. receive sts-3 transport ? receive sf set monitor interval ? byte 2 (address = 0x1131) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_set_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf set monitor interval ? byte 1 (address = 0x1132) bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 sf_set_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf set monitor interval ? byte 0 (address = 0x1133) bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 sf_set_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 0 once the user has executed these two steps, then the ?s f declaration criteria? (for the sf burst detector) will be as summarized below. ? b2 error threshold = 0x0f (or 15) b2 errors. ? sf set interval = 0x10 (or 16 sonet frame periods) hence, the receive sts-3 toh processor block will ac cumulate b2 errors over 16 sonet frame periods. at this point, the receive sts-3 toh processor block will proceed to coun t b2 errors. anytime the receive sts-3 toh processor block detects 15 or more b2 errors, within a 2ms period (e.g., 16 sonet frame periods); then it will declare the sf condition.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 382 sf clearance criteria ? per the ?b urst ? sf d etector in this case, the user specifies two parameters to define the sf clearance criteria. ? the maximum number of b2 errors (e.g., a b2 e rror-threshold) accumulated over a given ?sf clear interval? time period. ? the length (in terms of sonet frame periods ) of this ?sf clear interval? time period. once the user defines these parame ters, then the receive sts-3 toh pr ocessor block will begin to count the cumulative number of b2 errors that it detects within a ?sliding window? of time. the length of this ?sliding window of time? is dictated by the user -defined ?sf clear interval? time period. if the receive sts-3 toh processor block is currently decla ring the sf condition, and if it continues to detect more than the ?b2 error threshold? number of b2 errors; within the ?sf clear interval? of time, then it will not clear the sf condition. conversely , if the receive sts-3 toh processo r block detects less than the ?b2 error threshold? number of b2 errors, within the ?sf clear interval? of time, then it will clear the sf condition. s pecifying the ?b2 e rror t hreshold ? for c learing sf ? t he sf ?b urst ? d etector the user can specify the ?b2 error threshold? by wr iting the appropriate value into the ?receive sts-3 transport ? receive sf burst error tolerance ? byte 1 and byte 0? registers, as depicted below. receive sts-3 transport ? receive sf burst error tolerance ? byte 1 (address = 0x1156) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_burst_tolerance[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3 transport ? receive sf burst error tolerance ? byte 0 (address = 0x1157) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_burst_tolerance[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 notes: the ?receive sts-3 transport- receive sf burst error toleranc e ? byte 1 and byte 0? registers permit the user to write in a 16-bit expression for the ?b2 error threshold?. the ?default? value for the ?b2 error threshold? is ?0xffff?. the ?receive sts-3 transport ? receive sf burst error tolera nce? registers are used to set both the ?sf declaration? and ?sf clearance? criteria. therefore, any value that the user writes into this register (to set the ?sf clearance? criteria ? per the ?sf burst? detector) will also effect the ?sf declaration? criteria (per the ?sf burst? detector).
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 383 s pecifying the ?sf c lear i nterval ? of t ime likewise, the user can specify the ?sf clear interval? per iod by writing the appropriate value into the ?receive sts-3 transport ? receive sf clear monitor interval ? byte 2, 1 and 0? registers, as depicted below. receive sts-3 transport ? receive sf clear monitor interval ? byte 2 (address = 0x115d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3 transport ? receive sf clear monitor interval ? byte 1 (address = 0x115e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 receive sts-3 transport ? receive sf clear monitor interval ? byte 0 (address = 0x115f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 1 1 1 1 1 1 notes: the ?receive sts-3 transport ? receive sf clear monitor interv al ? byte 2, byte 1 and byte 0? registers permit the user to write in a 24-bit expression for the ?sf clear interval?. the number that is written into these registers represents the duration of the ?sd clear interval? periods, in terms of sonet frame periods. the actual length of time t hat the receive sts-3 toh processor block will us e (to accumulate b2 errors) to declare the sf condition is the value written into these registers. examples of defining the sf clearance cr iteria ? per the ?sf burst? detector suppose that the user writes in the value ?0x0008? in to the ?receive sts-3c transport ? receive sf burst error tolerance? registers; as depicted below. receive sts-3 transport ? receive sf burst error tolerance ? byte 1 (address = 0x1156) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_burst_tolerance[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf burst error tolerance ? byte 0 (address = 0x1157) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_burst_tolerance[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 1 0 0 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 384 additionally, now suppose that the user writes in the value ?0x000100? into the ?receive sts-3 transport ? receive sf clear monitor interval? registers; as depicted below. receive sts-3 transport ? receive sf clear monitor interval ? byte 2 (address = 0x115d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_monitor_window[23:16] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive sts-3 transport ? receive sf clear monitor interval ? byte 1 (address = 0x115e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_monitor_window[15:8] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 1 receive sts-3 transport ? receive sf clear monitor interval ? byte 0 (address = 0x115f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 sf_clear_monitor_window[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 once the user has executed these two steps, then the ?sf clearance criteria? will be as summarized below. ? b2 error threshold = 0x08 (or 8) b2 errors ? sf clear interval = 0x100 (or 256 sonet frame periods) hence, the receive sts-3 toh processor block will ac cumulate b2 errors over 256 sonet frame periods. at this point, the receive sts-3 toh processor block will proc eed to count b2 errors. if the receive sts-3 toh processor block is currently declaring the sf condition; it will now clear the sf condition if it detects less than 8 b2 errors, within a 32ms period (e.g., 256 sonet frame periods); then it will clear the sf condition.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 385 2.3.1.15 handling/support of the incoming k1, k2 bytes 2.3.1.16 handling/support of the incoming line dcc (d4 ? d12) bytes 2.3.1.17 handling/support of the incoming s1 byte 2.3.1.18 handling/support of the incoming m1 byte 2.3.1.19 handling/support of the incoming e2 byte 2.3.1.20 receive sts-3 toh processor block interrupts as described throughout much of this section the receive sts-3 toh processor block will generate an interrupt in response to any of the following conditions. ? change in the los defect condition ? change in the sef defect condition ? change in the lof defect condition ? change in the ais-l defect condition ? change in the sd defect condition ? change in the sf defect condition ? change in the section-trace me ssage mismatch defect condition 2.3.1.20.1 change of los defect condition interrupt 2.3.1.20.2 change of sef defect condition interrupt 2.3.1.20.3 change of lof defect condition interrupt 2.3.1.20.4 change of ais-l defect condition interrupt 2.3.1.20.5 detection of b1 byte error interrupt 2.3.1.20.6 detection of b2 byte error interrupt 2.3.1.20.7 change of sd (signal de grade) defect condition interrupt 2.3.1.20.8 change of sf (sig nal fail) defect condition 2.3.1.20.9 detection of rei-l interrupt 2.3.1.20.10 change of section trac e message mismatch defect condition 2.3.1.20.11 change of sec tion trace message unst able defect condition 2.3.1.21 receive sts-3 to h processor block per formance monitoring parameters the xrt94l33 supports performance monitoring by provid ing 32-bit reset-upon-read registers, that track the following parameters. ? b1 byte errors ? b2 byte errors ? number of rei-l events
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 386 2.3.2 receive sts-3 c poh processor block ( for sts-3 c a pplications ) the purpose of the receive sts-3c poh processor block is to accomplish the following. ? to receive an sts-3c spe from t he receive sts-3 to h processor block ? to acquire and maintain the location of the st s-3c spe, within the inco ming sts-3c data-stream ? to compute and verify the b3 bytes and increment performance monitor registers anytime it detects b3 byte errors. ? to declare and clear the following defect conditions. - lop-p (loss of pointer) - ais-p (path ais) - rdi-p (path ? remote defect indicator) - plm-p (path ? payload label mismatch) - uneq-p (path ? unequipped) - tim-p (path ? trace identification mismatch) ? to increment performance monitor regi sters anytime it detects an rei-p event. ? to receive either 1-byte, 16-byte or 64-byte path tr ace identification messages vi a the j1 byte within each incoming sts-3c spe; and to detect and declare the tim-p defect condition when appropriate. figure 90 presents an illustration of the functional block diagram of the xrt94l33 mapper ic; with the ?receive sts-3c poh processor? block highlighted.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 387 figure 90 illustration of the functi onal block diagram of the xrt94l33 mapper ic; with the receive sts-3c poh processor block highlighted transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3/12 toh processor block receive sts-3/12 toh processor block transmit sts-3/12 toh processor block transmit sts-3/12 toh processor block receive sts-3/12 poh processor block receive sts-3/12 poh processor block transmit sts-3/12 poh processor block transmit sts-3/12 poh processor block sts-3/12 telecom bus interface block sts-3/12 telecom bus interface block sts-3/12 pecl interface block sts-3/12 pecl interface block sts-3/12 cdr block sts-3/12 cdr block xrt95l34 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block the operation of the ?receive sts-3c poh processor? block is discussed in some detail below. 2.3.2.1 pointer processing as the xrt94l33 receives an incoming sts-3 data-st ream, the receive sts-3 toh processor block has the responsibility of de-scrambling this incomi ng data-stream, and acquiring and maintaining frame synchronization with the incoming sts-3 frames. on ce these incoming sts-3 frames have been located; the receive sts-3c poh processor block has the responsi bility of locating and keeping track of the sts-3c spes within this sts-3 data-stream. as required by the sonet/sdh standa rds, the receive sts-3c poh proc essor blocks accomplish this by monitoring the contents of each set of h1 and h2 bytes within the incoming sts-3 data-stream. if a given channel is receiving an sts-3c signal if a given channel is configured to receive an sts-3c signal, then each incoming sts-3 frame consists of a single sts-3c spe. the receive sts- 3c poh processor block determines th e location of this one sts-3c spe by the contents of the h1 and h2 byte t he toh of the incoming sts-3c data-stream. the h1 and h2 bytes within an sts-3c signal
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 388 2.3.2.1.1 handling incrementing pointer adjustment events 2.3.2.1.2 handling decrementing pointer adjustment events 2.3.2.1.3 handling ndf (new data flag) events 2.3.2.1.4 lop-p declaration and clearance criteria 2.3.2.1.5 ais-p declaration and clearance criteria 2.3.2.2 processing/hand ling the g1 byte 2.3.2.2.1 rdi-p detectio n and clearance criteria 2.3.2.2.2 detecting/flagging rei-p events the receive sts-3c poh processor bloc k is capable of detecting the rei- p indicator, within the incoming sts-3c spe data-stream. as the receive sts-3c poh processor block receives a given sts-3c spe data- stream, it will monitor the contents within bits _ through _ in the g1 byte. the bit-format of the g1 byte is presented below in figure 91. figure 91 bit format of the g1 byte figure 91 indicates that bits _ through _, within t he g1 byte are allocated for the rei-p function. the role of the rei-p bit-fields was described in some detail, in section _. this section indicates that the remote pte will set the ?rei-p? value (within the g1 byte ) to ?0? during ?un-erred? conditions. however, the remote pte will typically set the ?rei-p? value to a va lue (ranging from ?1? to ?8?) during ?erred? conditions. if the receive sts-3c poh processor block receives an sts-3c spe, that contains a ?non- zero? value of rei-p, then it will do the following. 1. it will generate the ?detec tion of rei-p event? interrupt. note: the receive sts-3c poh processor block will indicate this by, pulling the ?int*? output pin ?low? and by setting bit 6 (detection of rei-p event interrupt status), within the ?rec eive sts-3c path ? sonet receive path interrupt status ? byte 1? to ?1? as depicted below. receive sts-3c path ? sonet receive path interrupt status ? byte 1 (address = 0x118a) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused detection of rei-p event interrupt status change in uneq-p defect condition interrupt status change in plm-p defect condition interrupt status new c2 byte interrupt status change in c2 byte unstable defect condition interrupt status change in rdi-p unstable defect condition interrupt status new rdi-p value interrupt status r/o rur rur rur rur rur rur rur 0 1 0 0 0 0 0 0 2. it will increment the ?receive st s-3c path ? rei-p error count? registers note: these registers are actually 32-bit registers, which are located at direct address locations 0xna9c through 0xna9f. the bit-format of these registers is presented below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 389 receive sts-3c path ? rei-p error count register ? byte 3 (address = 0x119c) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rei_p_error_count[31:24] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive sts-3c path ? rei_p error count register ? byte 2 (address = 0x119d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rei_p_error_count[23:16] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive sts-3c path ? rei_p error count register ? byte 1 (address = 0x119e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rei_p_error_count[15:8] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive sts-3c path ? rei_p error count register ? byte 0 (address = 0x119f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rei_p_error_ count[7:0] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 note: the receive sts-3c poh processor block will increment t hese registers either by th e number of erred sts-3c spe (e.g., sts-3c spes with a non-zero rei-p value) detect ed, or by the value of t he rei-p value, within a given sts-3c frame; depending upon us er selection, as described below. configuring the receive sts-3c poh processor blo ck to increment the ?receive sts-3c path ? rei-p error count? register on a ?per-sts-3c spe? basis. the user can configure the receive sts-3c toh proces sor block to increment the ?receive sts-3c path ? rei-p error count? register, by the value ?1? for each sts-3c spe that contains a ?non-zero? rei-p value. the user can accomplish this by setting bit 1 (rei-p e rror type), within the ?receive sts-3c path ? control register ? byte 0? to ?1? as illustrated below. receive sts-3c path ? control register ? byte 0 (address = 0x1183) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused check stuff rdi-p type rei-p error type b3 error type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 1 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 390 configuring the receive sts-3c poh processor blo ck to increment the ?receive sts-3c path ? rei-p error count? register on an ?rei-p value? basis. the user can configure the receive sts-3c toh proces sor block to increment the ?receive sts-3c path ? rei-p error count? register by t he contents within the ?rei-p? nibbles , within each incoming sts-3c spe. therefore, in this mode, it is possible for the receiv e sts-3c poh processor block to increment this register by as much as the value ?8? per sts-3c spe. the user can accomplish this by setting bit 1 (rei-p error type) within the ?receive sts-3c path ? control register ? byte 0? to ?0?, as illustrated below. receive sts-3c path ? control register ? byte 0 (address = 0x1183) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused check stuff rdi-p type rei-p error type b3 error type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.3.2.3 path bip-8 (b3) byte verification configuring the receive sts-3c poh processor block to increment the ?receive sts-3c path ? b3 error count? register on a ?per-spe? basis. the receive sts-3c poh processor block has the resp onsibility for computing and verifying the path bip-8 (e.g., b3) byte within each incoming sts-3c spe. w hen the receive sts-3c poh processor block executes this function, it will do the following. ? it will read in the contents of a given ?newly received? sts-3c spe. ? it will compute the bip-8 value over the spe. ? this resulting bip-8 value will be compared with the contents of the b3 byte, within the very next sts-3c spe. the user can configure the receive sts-3c poh proces sor block to increment the ?receive sts-3c path ? b3 error count? register, by the value ?1? for each sts-3c spe that it determined to have a bit-error. the user can accomplish this by setting bit 0 (b3 erro r type), within the ?receive sts-3c path ? control register ? byte 0? to ?1?, as illustrated below. receive sts-3c path ? control register ? byte 0 (address = 0x1183) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused check stuff rdi-p type rei-p error type b3 error type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 1 note: this the user implements this setting, then the corres ponding transmit sts-3c poh processor block will set the rei-p nibble value (w ithin the g1 byte) to the number of erred spe that have been detected. in this case, the maximum value that the rei-p nibble (wit hin an sts-3c spe) will contain will be ?1?. if the receive sts-3c poh processor block detects any b3 byte errors, then it will do the following. a. it will generate the ?detection of b3 error? inte rrupt, by toggling the ?int*? output pin ?low? and by setting bit 7 (detection of b3 byte error interrupt status) to ?1? as indicated below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 391 receive sts-3c path ? sonet receive path interrupt status ? byte 0 (address = 0x118b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 detection of b3 byte error interrupt status detection of new pointer interrupt status detection of unknown pointer interrupt status detection of pointer decrement interrupt status detection of pointer increment interrupt status detection of ndf pointer interrupt status change of lop-p condition interrupt status change of ais-p condition interrupt status rur rur rur rur rur rur rur rur 1 0 0 0 0 0 0 0 b. it will increment the ?receive sts-3c path ? b3 error count? register s. the ?receive sts-3c path ? b3 error count? register is actually a 32 bit regist er that resides at direct address 0xna98 ? 0xna9b. note: the receive sts-3c poh processor block will increment t hese registers either by th e number of erred sts-3c spes detected, or by the number of b3 bits that are detected to be in error (within a given sts-3c frame), depending upon user selection, as described below. configuring the receive sts-3c poh processor block to increment the ?receive sts-3c path ? b3 error count? register on a ?per b3 bit-error? basis the user can configure the receive sts-3c poh proces sor block to increment the ?receive sts-3c path ? b3 error count? register by the numbe r of ?b3 bits? which are determined to be in error. therefore, in this mode, it is possible for the receive sts-3c poh processor block to increment this register by as much as the value of ?8? per sts-3c spe. the user can accomplish this by setting bit 0 (b3 erro r type) within the ?receive sts-3c path ? control register ? byte 0? to ?0?, as illustrated below. receive sts-3c path ? control register ? byte 0 (address = 0x1183) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused check stuff rdi-p type rei-p error type b3 error type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 1 note: if the user implements this setting, then the corresponding transmit sts-3c poh processor block will set the rei-p nibble value (within the g1 byte) to the number of b3 bits that have been determined to be in error. in this case, the rei-p nibble value can contain a number as high as ?8? for each ?outbound? sts-3c frame. the detection of b3 byte errors also plays a role in the transmission of the rei-p (path ? remote error indicator) back out to the remote terminal equipment. this item will be discussed in some detail in section _. 2.3.2.4 handling/processing the c2 byte 2.3.2.4.1 uneq-p declaration and clearance criteria 2.3.2.4.2 plm-p declaration and clearance criteria 2.3.2.5 receiving/processing incoming path trace messages via the j1 byte 2.3.2.5.1 tim-p declaration and clearance criteria 2.3.2.5.2 path trace unstable defect declaration and clearance criteria
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 392 2.3.2.6 receiving/processing the f2 byte within the incoming sts-3 c spe data stream 2.3.2.7 receiving/processing the h4 byte within the incoming sts-3 c spe data stream 2.3.2.8 receving/processing the z3 byte within the incoming sts-3 c spe data- stream 2.3.2.9 receiving/processing the z4 byte within the incoming sts-3 c spe data- stream 2.3.2.10 receiving/processing the z5 byte within the incoming sts-3 c spe data- stream 2.3.2.11 interrupt processing within the receive sts-3 c poh processor block 2.3.2.11.1 change of lop-p defect condition interrupt 2.3.2.11.2 change of ais-p defect condition interrupt 2.3.2.11.3 detection of b3 byte error interrupt 2.3.2.11.4 change of uneq-p defect condition interrupt 2.3.2.11.5 change of plm-p defect condition interrupt 2.3.2.11.6 detection of rei-p interrupt 2.3.2.11.7 change of tim-p defect condition interrupt 2.3.2.11.8 change of path trace m essage unstable condition interrupt 2.3.2.12 performance monitoring with the receive sts-3 c poh processor block
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 393 2.3.3 receive sonet poh processor block the purpose of the receive sonet poh processor block is to accomplish the following. ? to receive an sts-1 spe from the receive sts-3 toh processor block ? to acquire and maintain the location of the sts-1 spe, within the incoming sts-1 data-stream ? to compute and verify the b3 bytes and increment performance monitor registers anytime it detects b3 byte errors. ? to declare and clear the following defect conditions. - lop-p (loss of pointer) - ais-p (path ais) - rdi-p (path ? remote defect indicator) - plm-p (path ? payload label mismatch) - uneq-p (path ? unequipped) - tim-p (path ? trace identification mismatch) ? to increment performance monitor regi sters anytime it detects an rei-p event. ? to receive either 1-byte, 16-byte or 64-byte path tr ace identification messages vi a the j1 byte within each incoming sts-1 spe; and to detect and declare the tim-p defect condition when appropriate. figure 92 presents an illustration of the functional block diagram of the xrt94l33 mapper ic; with the ?receive sonet poh processor? block highlighted.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 394 figure 92 illustration of the functi onal block diagram of the xrt94l33 mapper ic; with the receive sonet poh processor block highlighted transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3/12 toh processor block receive sts-3/12 toh processor block transmit sts-3/12 toh processor block transmit sts-3/12 toh processor block receive sts-3/12 poh processor block receive sts-3/12 poh processor block transmit sts-3/12 poh processor block transmit sts-3/12 poh processor block sts-3/12 telecom bus interface block sts-3/12 telecom bus interface block sts-3/12 pecl interface block sts-3/12 pecl interface block sts-3/12 cdr block sts-3/12 cdr block xrt95l34 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block 2.3.3.1 pointer processing as the xrt94l33 receives an incoming sts-3 data-st ream, the receive sts-3 toh processor block has the responsibility of de-scrambling this incomi ng data-stream, and acquiring and maintaining frame synchronization with the incoming sts-3 frames. on ce these incoming sts-3 frames have been located; the receive sonet poh processor block ha s the responsibility of locating and keeping tr ack of the sts-1 spes within this sts-3 data-stream. as required by the sonet/sdh stan dards, the receive sonet poh processor blocks accomplish this by monitoring the contents of each set of h1 and h2 bytes within the incoming sts-3 data-stream. if a given channel is receiving an sts-1 signal if a given channel is configured to receive an sts-1 si gnal, then each incoming sts-3 frame consists of a single sts-1 spe. the receive sone t poh processor block determines the location of this one sts-1 spe by the contents of the h1 and h2 byte the toh of the incoming sts-1 data-stream. the h1 and h2 bytes within an sts-1 signal
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 395 2.3.3.1.1 handling incrementing pointer adjustment events 2.3.3.1.2 handling decrementing pointer adjustment events 2.3.3.1.3 handling ndf (new data flag) events 2.3.3.1.4 lop-p declaration and clearance criteria 2.3.3.1.5 ais-p declaration and clearance criteria 2.3.3.2 processing/hand ling the g1 byte 2.3.3.2.1 rdi-p detectio n and clearance criteria 2.3.3.2.2 detecting/flagging rei-p events the receive sonet poh processor block is capable of detecting the rei-p indicator, within the incoming sts-1 spe data-stream. as the receive sonet poh processor block receives a given sts-1 spe data- stream, it will monitor the contents within bits _ through _ in the g1 byte. the bit-format of the g1 byte is presented below in figure 93 figure 93 bit format of the g1 byte figure 93 indicates that bits _ through _, within t he g1 byte are allocated for the rei-p function. the role of the rei-p bit-fields was described in some detail, in section _. this section indicates that the remote pte will set the ?rei-p? value (within the g1 byte ) to ?0? during ?un-erred? conditions. however, the remote pte will typically set the ?rei-p? value to a va lue (ranging from ?1? to ?8?) during ?erred? conditions. if the receive sonet poh processor bloc k receives an sts-1 spe, that c ontains a ?non-zero? value of rei- p, then it will do the following. 1. it will generate the ?detec tion of rei-p event? interrupt. note: the receive sonet poh processor block will indicate th is by, pulling the ?int*? output pin ?low? and by setting bit 6 (detection of rei-p event interrupt status), within the ?r eceive sonet path ? sonet receive path interrupt status ? byte 1? to ?1? as depicted below. receive sonet path ? sonet receive path in terrupt status ? byte 1 (address = 0xn18a) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused detection of rei-p event interrupt status change in uneq-p defect condition interrupt status change in plm-p defect condition interrupt status new c2 byte interrupt status change in c2 byte unstable defect condition interrupt status change in rdi-p unstable defect condition interrupt status new rdi-p value interrupt status r/o rur rur rur rur rur rur rur 0 1 0 0 0 0 0 0 2. it will increment the ?receive sone t path ? rei-p error count? registers note: these registers are actually 32-bit registers, which ar e located at direct address locations 0xna9c through 0xna9f. the bit-format of these registers is presented below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 396 receive sonet path ? rei-p error count register ? byte 3 (address = 0xn19c) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rei_p_error_count[31:24] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive sonet path ? rei_p error count register ? byte 2 (address = 0xn19d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rei_p_error_count[23:16] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive sonet path ? rei_p error count register ? byte 1 (address = 0xn19e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rei_p_error_count[15:8] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive sonet path ? rei_p error count register ? byte 0 (address = 0xn19f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 rei_p_error_ count[7:0] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 note: the receive sonet poh processor block will increment t hese registers either by t he number of erred sts-1 spe (e.g., sts-1 spes with a non-zero rei-p value) detect ed, or by the value of the rei-p value, within a given sts-1 frame; depending upon user selection, as described below. configuring the receive sonet poh processor block to increment the ?receive sonet path ? rei-p error count? register on a ?per-sts-1 spe? basis. the user can configure the receive sts-1 toh proces sor block to increment the ?receive sonet path ? rei-p error count? register, by the value ?1? for each sts-1 spe that c ontains a ?non-zero? rei-p value. the user can accomplish this by setting bit 1 (rei-p e rror type), within the ?receive sonet path ? control register ? byte 0? to ?1? as illustrated below. receive sonet path ? control register ? byte 0 (address = 0xn183) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused check stuff rdi-p type rei-p error type b3 error type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 1 0 configuring the receive sonet poh processor block to increment the ?receive sonet path ? rei-p error count? register on an ?rei-p value? basis.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 397 the user can configure the receive sts-3 toh proces sor block to increment the ?receive sonet path ? rei-p error count? register by t he contents within the ?rei-p? nibbles , within each incoming sts-1 spe. therefore, in this mode, it is possible for the receiv e sonet poh processor block to increment this register by as much as the value ?8? per sts-1 spe. the user can accomplish this by setting bit 1 (rei-p error type) within the ?receive sonet path ? control register ? byte 0? to ?0?, as illustrated below. receive sonet path ? control register ? byte 0 (address = 0xn183) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused check stuff rdi-p type rei-p error type b3 error type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 0 2.3.3.3 path bip-8 (b3) byte verification configuring the receive sonet poh processor block to increment the ?receive sonet path ? b3 error count? register on a ?per-spe? basis. the user can configure the receive sonet poh proces sor block to increment the ?receive sonet path ? b3 error count? register, by the value ?1? for each sts-1 spe that it determined to have a bit-error. the user can accomplish this by setting bit 0 (b3 e rror type), within the ?receive sonet path ? control register ? byte 0? to ?1?, as illustrated below. receive sonet path ? control register ? byte 0 (address = 0xn183) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused check stuff rdi-p type rei-p error type b3 error type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 1 note: this the user implements this setting, then the corre sponding transmit sonet poh processor block will set the rei-p nibble value (w ithin the g1 byte) to the number of erred spe that have been detected. in this case, the maximum value that the rei-p nibble (wit hin an sts-1 spe) will contain will be ?1?. the receive sonet poh processor bloc k has the responsibility for comput ing and verifying the path bip-8 (e.g., b3) byte within each incomi ng sts-1 spe. when the receive so net poh processor block executes this function, it will do the following. ? it will read in the contents of a given ?newly received? sts-1 spe. ? it will compute the bip-8 value over the spe. ? this resulting bip-8 value will be compared with t he contents of the b3 byte, within the very next sts-1 spe. if the receive sonet poh processor block detects any b3 byte errors , then it will do the following. a. it will generate the ?detection of b3 error? inte rrupt, by toggling the ?int*? output pin ?low? and by setting bit 7 (detection of b3 byte error interrupt status) to ?1? as indicated below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 398 receive sonet path ? sonet receive path in terrupt status ? byte 0 (address = 0xn18b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 detection of b3 byte error interrupt status detection of new pointer interrupt status detection of unknown pointer interrupt status detection of pointer decrement interrupt status detection of pointer increment interrupt status detection of ndf pointer interrupt status change of lop-p condition interrupt status change of ais-p condition interrupt status rur rur rur rur rur rur rur rur 1 0 0 0 0 0 0 0 b. it will increment the ?receive sonet path ? b3 error count? regist ers. the ?receive sonet path ? b3 error count? register is actually a 32 bit regist er that resides at direct address 0xna98 ? 0xna9b. note: the receive sonet poh processor block will increment t hese registers either by t he number of erred sts-1 spes detected, or by the number of b3 bits that are detect ed to be in error (withi n a given sts-1 frame), depending upon user selection, as described below. configuring the receive sonet poh processor block to increment the ?receive sonet path ? b3 error count? register on a ?per b3 bit-error? basis the user can configure the receive sonet poh proces sor block to increment the ?receive sonet path ? b3 error count? register by the numbe r of ?b3 bits? which are determined to be in error. therefore, in this mode, it is possible for the receive sonet poh processo r block to increment this register by as much as the value of ?8? per sts-1 spe. the user can accomplish this by setting bit 0 (b3 er ror type) within the ?receive sonet path ? control register ? byte 0? to ?0?, as illustrated below. receive sonet path ? control register ? byte 0 (address = 0xn183) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused check stuff rdi-p type rei-p error type b3 error type r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 0 0 0 1 note: if the user implements this setting, then the corresp onding transmit sonet poh processor block will set the rei-p nibble value (within the g1 byte) to the number of b3 bits that have been determined to be in error. in this case, the rei-p nibble value can contain a number as high as ?8? for each ?outbound? sts-1 frame. the detection of b3 byte errors also plays a role in the transmission of the rei-p (path ? remote error indicator) back out to the remote terminal equipment. this item will be discussed in some detail in section _.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 399 2.3.3.4 handling/processing the c2 byte 2.3.3.4.1 uneq-p declaration and clearance criteria 2.3.3.4.2 plm-p declaration and clearance criteria 2.3.3.5 receiving/processing incoming path trace messages via the j1 byte 2.3.3.5.1 tim-p declaration and clearance criteria 2.3.3.5.2 path trace unstable defect declaration and clearance criteria 2.3.3.6 receiving/processing the f2 byte wi thin the incoming sts-1 spe data stream 2.3.3.7 receiving/processing the h4 byte within the incoming sts-1 spe data stream 2.3.3.8 receving/processing the z3 byte within the incoming sts-1 spe data- stream 2.3.3.9 receiving/processing the z4 byte wi thin the incoming sts-1 spe data- stream 2.3.3.10 receiving/processing the z5 byte wi thin the incoming sts-1 spe data- stream 2.3.3.11 interrupt processing within the receive sonet poh processor block 2.3.3.11.1 change of lop-p defect condition interrupt 2.3.3.11.2 change of ais-p defect condition interrupt 2.3.3.11.3 detection of b3 byte error interrupt 2.3.3.11.4 change of uneq-p defect condition interrupt 2.3.3.11.5 change of plm-p defect condition interrupt 2.3.3.11.6 detection of rei-p interrupt 2.3.3.11.7 change of tim-p defect condition interrupt 2.3.3.11.8 change of path trace m essage unstable condition interrupt 2.3.3.12 performance monitoring with the receive sonet poh processor block
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 400 2.3.4 receive atm cell processor block the next functional block, within the receive path is the receive atm cell processor block. figure 94 presents an illustration of the xrt94l33 functional bl ock diagram, with the ?rec eive atm cell processor? block highlighted. figure 94 illustration of the xrt94l33 functional block diagram, with the receive atm cell processor block highlighted transmit utopia interface block transmit utopia interface block receive utopia/ interface block receive utopia/ interface block transmit atm cell processor block transmit atm cell processor block receive atm cell processor block receive atm cell processor block transmit ppp processor block transmit ppp processor block receive ppp processor block receive ppp processor block receive sts-3/12 toh processor block receive sts-3/12 toh processor block transmit sts-3/12 toh processor block transmit sts-3/12 toh processor block receive sts-3/12 poh processor block receive sts-3/12 poh processor block transmit sts-3/12 poh processor block transmit sts-3/12 poh processor block sts-3/12 telecom bus interface block sts-3/12 telecom bus interface block sts-3/12 pecl interface block sts-3/12 pecl interface block sts-3/12 cdr block sts-3/12 cdr block xrt95l34 ? channel 0 transmit pos-phy interface block transmit pos-phy interface block receive pos-phy interface block receive pos-phy interface block clock synthesizer block clock synthesizer block microprocessor interface block microprocessor interface block figure 95 presents a simple block diagram of the receiv e atm cell processor block (with the external pins indicated). figure 95 simple illustration of the receive atm ce ll processor block and the associated external pins
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 401 a very brief description of the receive atm cell processor block the receive atm cell processor block receives an un- delineated stream of atm cell data from the receive sts-3c poh processor block. as this data-stream passes through the receive atm cell processor block it will initially pass through the ?hec byte verification? block which is responsible for cell delineation and hec byte verification. the receive atm cell processor receives a continuou s unframed stream of atm cells from the receive sts-3c poh processor block. as the receive atm cell processor block receives this atm cell data, it will then perform all of the following functions on this atm cell data. ? cell delineation ? hec byte verification ? cell payload de-scrambling (optional) ? idle cell filtering ? user cell filtering finally, all atm cells that successfully make it throu gh the ?above-mentioned? proc essing will be written into the ?rxfifo? within the receive utopia interface bl ock, where it can be read out via the receive utopia data bus (by the atm layer processor block). functional description of the receive atm cell processor this section presents an in-depth functional desc ription of the receive at m cell processor block. additionally, this section presents all of the configur ation options associated with the receive atm cell processor block. the receive atm cell processor block consists of the following functional blocks. ? hec byte verification block ? cell payload de-scrambler block ? idle cell filter block ? receive user cell filter block ? receive cell extraction buffer/processor ? receive cell insertion buffer/processor ? parity calculation and insertion block ? receive gfc nibble-field serial output port figure 96 presents an illustration of the functional block diagram of t he receive atm cell processor block with each of these ?above-mentioned? functional blocks noted. each of these ?sub-blocks? will be disc ussed in some detail below . however, before we get too much into the detailed functional description of the receive atm ce ll processor block; the user must note that the receive atm cell processor block will not even function unless the user enables the ?receive atm cell processor? block for operation. the user can enable the receive atm cell processor block by setting bit 1 (receive atm cell processor enable), within the ?rec eive atm cell processor block ? receive atm control register ? byte 2? to ?1? as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 402 receive atm cell processor block ? receive atm control register ? byte 2 (address = 0xn701) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused receive atm cell processor enable test cell receiver mode enable r/o r/o r/o r/o r/o r/o r/w r/w 0 0 0 0 0 0 1 0 figure 96 functional block diagram of the receive atm cell processor block parity calculation block parity calculation block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte verification block hec byte verification block cell payload de-scrambler block cell payload de-scrambler block rxfifo rxfifo receive utopia interface block microprocessor interface block microprocessor interface block idle cell filter idle cell filter main data path from receive sts-3c/sts-12c poh processor block receive gfc nibble-field output i/f receive gfc nibble-field output i/f each of these sub-blocks will be discussed in some detail below. 2.3.4.1 t he hec b yte v erification b lock the hec byte verification block is the very first bl ock (within the signal path of the receive atm cell processor block) to receive and proc ess atm cell data. figure 97 presents an illustration of the ?functional block diagram? of the receive atm cell processor bloc k with the ?hec byte verification? block highlighted.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 403 figure 97 illustration of the ?functional block diagram? of the receive atm cell processor block with the hec byte verification? block highlighted parity calculation block parity calculation block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte verification block hec byte verification block cell payload de-scrambler block cell payload de-scrambler block rxfifo rxfifo receive utopia interface block microprocessor interface block microprocessor interface block idle cell filter idle cell filter main data path from receive sts-3c/sts-12c poh processor block receive gfc nibble-field output i/f receive gfc nibble-field output i/f the hec byte verification block will receive an un-deli neated stream of atm cells, from the receive sts-3c poh processor block. as the hec byte verification bl ock receives this data-stream it is responsible for performing the following two functions, wi thin the receive atm cell processor block ? cell delineation ? hec byte verification each of these functions is described in some detail below. 2.3.4.1.1 acquiring and maintaining cell delinea tion with the incoming atm cell data-stream as the receive sts-3c poh processor block receives the incoming sts-3c spe data, the contents of these sts-3c spes will be extracted out an d will be routed to th e receive atm cell proces sor block for further processing. in atm applications, the contents of ea ch of these sts-3c spes are atm cells. as the hec byte verification block receives this stream of atm cells, this atm ce ll data will initially be ?unframed?. therefore, the hec byte verification block will have to use the ?hec byte ? cell-delineation algorithm in order to locate the boundaries of these cells. the hec byte cell delineati on algorithm contains three states: hunt, presync and sync, as depicted in the state machine diagram in fi gure 98. each of these three states is discussed below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 404 figure 98 cell delineation algorithm employed by the receive atm cell processor block hunt presync sync correct hec incorrect hec delta consecutive correct hec at 53 byte intervals alpha consecutive incorrect hec the hunt state when the xrt94l33 is first powered up and is configured in the atm mode, then the hec byte verification block will initially be operating in the ?hunt? state. while the hec byte ve rification block is operating in the ?hunt? state, it has no knowledge of th e location of the boundaries of the in coming cells. in the hunt state, the hec byte verification block is searching through th e incoming (?unframed?) cell data-stream for a possible valid cell header pattern (e.g., one that does not produce a he c byte error). therefore, while in this state, the hec byte verification will read in five octets of t he data that it receives from the receive sts-3c poh processor block. the hec byte ve rification block will then compute a ?hec byte value? based upon the first four of these five octets. the he c byte verification block will then co mpare this interna lly computed value with that of the 5 th ?read-in? octet. if the two values are not the sa me, then the hec byte ve rification block will conclude that it has not located the boundaries of t he atm cells within the incoming data-stream and will increment its sampling set (of the 5 bytes, within the incoming data-stream) by one bit, and will repeat the above-mentioned process with this new set of ?candidate? header bytes. in other words, the hec byte verification block obtains its next selecti on of five octets, 53 bytes and 1 bit later. if the hec byte verification block comes across a set of five octets, that are such that the computed hec byte value does match the 5 th (read in) octet, then the hec byte veri fication block will transition into the presync state. the pre-sync state the hec byte verification block will transition from t he ?hunt? state to the ?presync? state; when it has located an ?apparently? valid set of cell header bytes. howe ver, it is possible that the hec byte verification block is being ?fooled? by user data that simply mimi cs the cell header byte pattern. therefore, further evaluation is required in order to confirm that this set of five octets are truly valid cell header bytes. the purpose of the ?pre-sync? state is to facilitate this further evaluation.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 405 when the hec byte verification block is operating in the pre-sync state, it will then begin to sample five (5) ?candidate header bytes? from the data within the in coming data-stream, repeatedly at 53 byte intervals. during this sampling process, the hec byte verificati on block will compute and compare its newly computed ?hec byte value? with that of the fifth (read-in) octet. if the hec byte verification block, while operating in the pre-sync state, comes across a single invalid cell heade r byte pattern, then the hec byte verification block will transition back to the ?hunt? state. however, if the hec byte verification block detects ?delta? consecutive valid cell byte headers, then it will transition into the sync state. the sync state once the hec byte verification block has transitioned into the ?sync? state, then this means that the receive atm cell processor block is ?officially? deli neation atm cells. the receive atm cell processor block will notify the microproce ssor (and external circuitry) of this transition into the sync state by doing all of the following. 1. it will indicate that it as cleared the lcd defect condition by setting bit 0 (lcd defect declared) and the bits 2 and 1 (cell delineation status[1:0]) bit-fields, within the ?receive atm cell processor block ? receive atm status register? to ?0?, as depicted below. receive atm cell processor block ? receive atm status register (address = 0xn707) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused prbs lock indicator cell delineation status[1:0] lcd defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 0 0 0 2. it will generate the ?clearance of lcd defect cond ition? interrupt. the receive atm cell processor block will indicate that it is declaring the ?clearance of lcd defect condition? interrupt by doing the following. - toggling the ?int*? output pin ?low?. - setting bit 1 (clearance of lcd defect interrupt status), within the ?receive atm cell processor block ? receive atm interrupt status re gister ? byte 0? to ?1? as depicted below. receive atm cell processor block ? receive atm interrupt status register ? byte 0 (address = 0xn70b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive cell insertion interrupt status receive fifo overflow interrupt status receive cell extraction memory overflow interrupt status receive cell insertion memory overflow interrupt status detection of correctable hec byte error interrupt status detection of uncorrectable hec byte error interrupt status clearance of lcd defect interrupt status declaration of lcd defect interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 0 0 1 0 whenever the hec byte verification bl ock is operating in the sync state, it will tolerate a certain number of errors in the header bytes of the incoming cells. additi onally, in some case, the hec byte verification block will even attempt to correct some of t hese errors. however, the occurrence of ?alpha? consec utive cells with header byte errors (single or multi-bit) will cause the hec byte verification block to return to the ?hunt? state. if this were to occur, then the receive atm cell processor block will notify the external circuitry that it is not properly delineating cells by doing the following.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 406 1. it will indicate that it has decla red the lcd defect condition by setti ng bit 0 (lcd defe ct declared) and bits 2 and 1 (cell delineation status[1:0]) bit-fields , within the ?receive atm cell processor block ? receive atm status register to ?1? as depicted below. receive atm cell processor block ? receive atm status register (address = 0xn707) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused prbs lock indicator cell delineation status[1:0] lcd defect declared r/o r/o r/o r/o r/o r/o r/o r/o 0 0 0 0 0 1 1 1 2. it will generate the ?declaration of lcd defect co ndition? interrupt. the receive atm cell processor block will indicate that it is declaring the ?decla ration of lcd defect condition? interrupt by doing the following. a. toggling the ?int*? output pin ?low?. b. setting bit 0 (declaration of lcd defect in terrupt status), within the ?receive atm cell processor block ? receive atm interrupt status re gister ? byte 0? to ?1? as depicted below. receive atm cell processor block ? receive atm interrupt status register ? byte 0 (address = 0xn70b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive cell insertion interrupt status receive fifo overflow interrupt status receive cell extraction memory overflow interrupt status receive cell insertion memory overflow interrupt status detection of correctable hec byte error interrupt status detection of uncorrectable hec byte error interrupt status clearance of lcd defect interrupt status declaration of lcd defect interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 1 the remaining discussion of the receive atm cell processo r block, within this data sheet, presumes that it (the receive atm cell processor block) is operating in the ?sync? state and properly delineating cells. once the receive atm cell processor is properly delineat ing cells then it will proceed to route these cells through a series of ?filters?; prior to allowing these cells to be written to the rxfifo within the receive utopia interface block. ultimately, the sequence of filtering/ processing that each cell must go through is listed below in sequential order. ? hec byte verification ? idle cell filtering ? user cell filtering ? cell payload de-scrambling the next few sections discusses each of these forms of ?cell filtering?.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 407 2.3.4.1.2 hec byte verification once the hec byte verification block is properly delineating cells, then the hec byte verification block will (as its name implies) perform ?hec by te verification? of incoming cells data from the receive sts-3c poh processor block in order to protect against misrouted or mis-inserted cells. in performing hec byte verifi cation the hec byte verification block w ill take the first four byte of each cells (e.g., the header bytes) and will independently comput e its own value for the hec byte. afterwards, the hec byte verification block will compare its value of the hec byte with the fi fth octet that it has received from the receive sts-3c poh processor block. if the two ?hec byte? values match then the ?receive atm cell processor? block will retain this cell for further processi ng. however, if the hec byte verification block detects errors in the header bytes of a cell, then the hec byte verification block will call up and employ the ?hec byte error correction/detection? algorithm (see below). the hec byte verification block will compute its versio n of the hec byte via t he generating polynomial x 8 + x 2 + x + 1. the user should be aware that the hec bytes of the incoming cell might have been modulo-2 added with the coset polynomial x 6 + x 4 + x 2 + 1. if this is the case then the receive atm cell processor block must be configured to account for this by writing a ?1? to bit 1 (coset polynomial addition) within the ?receive atm cell processor block ? receive atm control register ? byte 1. receive atm cell processor block ? receive atm control register ? byte 1 (address = 0xn702) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused gfc extraction enable hec byte correction enable uncorrectable hec byte error discard coset polynomial addition regenerate hec byte enable r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0 1 0 1 0 the ?hec byte error correction/detection? algorithm if the hec byte verification block detects one or more errors in the header bytes of a given incoming atm cell, then the ?hec byte error correction/detection? algorithm will be employed. the ?hec byte error correction/detection? algorithm has two states : ?detection? mode and ?correction? mode. figure 99 presents a state machine diagram of the ?hec byte error correction/detection? algorithm. each of these states is discussed below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 408 figure 99 state machine diagram of the hec byte error correction/detection algorithm correction mode detection mode no error detected multi-bit error detected (cell discarded) no error detected for m consecutive cells single-bit error detected (cell corrected) error detected (cell discarded) alpha consecutive cells with incorrect hec bytes (to hunt state) the ?correction? state when the hec byte verification block is operating within the ?correction? state, within the ?hec byte error correction/detection? algorithm, then cells that contain single bit errors (within the header bytes) will be corrected. however, cells with multiple bit erro rs are discarded, unless configured by the user. note: the user can configure the receive atm cell processor blo ck to retain cells that contain multi-bit errors, by setting bit 2 (uncorrectable hec byte error discard), within the ?receive atm cell processor block ? receive atm control register ? byte 1? register, to ?0?, as depicted below. receive atm cell processor block ? receive atm control register ? byte 1 (address = 0xn702) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused gfc extraction enable hec byte correction enable uncorrectable hec byte error discard coset polynomial addition regenerate hec byte enable r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0 1 0 1 0 if the hec byte verification block is operating in the ?c orrection state? then it will do all of the following anytime it detects any incoming atm cells that contain header byte errors.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 409 if the hec byte verification block detects a single-bi t error within the header bytes of an atm cell: 1. it will generate the ?detection of correctable hec byte error? interr upt. the receive at m cell processor block will indicate that it is decla ring the ?detection of correctable he c byte error? interrupt, by doing the following. a. toggling the ?int*? output pin ?low?. b. setting bit 3 (detection of correctable hec byte erro r interrupt status), within the ?receive atm cell processor block ? receive atm interrupt status re gister ? byte 0? to ?1? as depicted below. receive atm cell processor block ? receive atm interrupt status register ? byte 0 (address = 0xn70b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive cell insertion interrupt status receive fifo overflow interrupt status receive cell extraction memory overflow interrupt status receive cell insertion memory overflow interrupt status detection of correctable hec byte error interrupt status detection of uncorrectable hec byte error interrupt status clearance of lcd defect interrupt status declaration of lcd defect interrupt status rur rur rur rur rur rur rur rur 0 0 0 0 1 0 0 0 2. it will increment the ?receive atm cell processo r block ? receive atm cell with correctable hec byte error count? regi sters. this is 32-bit reset-u pon-read register that reside s at address locations 0xn730 through 0xn733. the bit format of these registers is presented below. receive atm cell processor block ? receive atm cells with correctable hec byte error count register ? byte 3 (address = 0xn730) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received cells with correctable hec byte error count[31:24] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive atm cells with correctable hec byte error count register ? byte 2 (address = 0xn731) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received cells with correctable hec byte error count[23:16] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive atm cells with correctable hec byte error count register ? byte 1 (address = 0xn732) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received cells with correctable hec byte error count[15:8] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive atm cells with correctable hec byte error count register ? byte 0 (address = 0xn733)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 410 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received cells with correctable hec byte error count[7:0] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 3. it will correct the ?single-bit? e rror within this particular atm cell. 4. the ?hec byte verification? block w ill transition into the ?detection? mode. if the hec byte verification block detects a multi- bit error within the header bytes of an incoming atm cell: 1. it will generate the ?detection of uncorrectable hec byte error? interrupt. the receive atm cell processor block will indicate that it is declaring the ?d etection of uncorrectable he c byte error? interrupt, by doing the following. a. toggling the ?int*? output pin ?low?. b. setting bit 2 (detection of uncorrectable hec byte error interrupt status), within the ?receive atm cell processor block ? receive atm interrupt status register ? byte 0? to ?1? as depicted below. 2. it will increment the ?receive atm cell processor block ? receive atm cell with uncorrectabl e hec byte error count? registers. this is a 32-bit reset-upon- read register that resi des at address locations 0xn734 through 0xn737. the bit format of these registers is presented below. receive atm cell processor block ? receive atm cells with uncorrectable hec byte error count register ? byte 3 (address = 0xn734) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received cells with uncorrectable hec byte error count[31:24] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive atm cells with uncorrectable hec byte error count register ? byte 2 (address = 0xn735) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received cells with uncorrectable hec byte error count[23:16] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive atm cells with uncorrectable hec byte error count register ? byte 1 (address = 0xn736) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received cells with uncorrectable hec byte error count[15:8] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive atm cells with uncorrectable hec byte error count register ? byte 0 (address = 0xn737) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 411 received cells with uncorrectable hec byte error count[7:0] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 3. it will not correct the ?single-bit? error within th is particular atm cell. in fact, unless the receive atm cell processor block is configur ed otherwise, it will discard this particular atm cell. note: whenever the receive atm cell processor block discards atm cells for ?uncorrectable hec byte? errors it will also increment the ?receive atm cell processor block ? receive discarded atm cell count? registers. these registers are also 32-bit reset-upon-read registers t hat reside at address locations 0xn72c through 0xn72f. the bit format of these registers is presented below. receive atm cell processor block ? receive discarded atm cell count ? byte 3 (address = 0xn72c) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive ? discarded atm cell count[31:24] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive discarded atm cell count ? byte 2 (address = 0xn72d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive ? discarded atm cell count[23:16] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive discarded atm cell count ? byte 1 (address = 0xn72e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive ? discarded atm cell count[15:8] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive discarded atm cell count ? byte 0 (address = 0xn72f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive ? discarded atm cell count[7:0] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 4. the hec byte verification block w ill transition into the ?detection? mode. the user can enable or disable entry into, and operation within the ?correction? mode by setting bit 3 (hec byte correction enable) within the ?receive atm ce ll processor block ? receive atm control register ? byte 1?, to the appropriate value as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 412 receive atm cell processor block ? receive atm control register ? byte 1 (address = 0xn702) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused gfc extraction enable hec byte correction enable uncorrectable hec byte error discard coset polynomial addition regenerate hec byte enable r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0 x 0 1 0 setting this bit-field to ?0? disables ?correction mode? operation within the hec by te verification block. conversely, setting this bit-field to ?1? enables ?corre ction mode? operation within the hec byte verification block. the ?detection? state unless ?correction mode? operation is disabled (per the procedure descri bed above), the hec byte verification block will transition into the ?detection? st ate (within the ?hec byte error detection/correction? algorithm. whenever the ?hec byte verification? block is operating in the ?detection? state, then all errored cells (e.g., those incoming cells that contain singl e-bit errors and multi-bit errors) w ill be discarded, un less configured otherwise by the user. more specifically, whenever the hec byte verification bl ock detects any cells with header byte errors, then it will do all of the following. 1. it will generate the ?detection of uncorrectable hec byte error? interrupt. the receive atm cell processor block will indicate that it is declaring the ?d etection of uncorrectable he c byte error? interrupt, by doing the following. a. toggling the ?int*? output pin ?low?. b. setting bit 2 (detection of uncorrectable hec byte error interrupt status), within the ?receive atm cell processor block ? receive atm interrupt status register ? byte 0? to ?1? as depicted below. 2. it will increment the ?receive atm cell processor block ? receive atm cell with uncorrectabl e hec byte error count? registers. this is a 32-bit reset-upon- read register that resi des at address locations 0xn734 through 0xn737. the bit format of these registers is presented below. receive atm cell processor block ? receive atm cells with uncorrectable hec byte error count register ? byte 3 (address = 0xn734) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received cells with uncorrectable hec byte error count[31:24] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive atm cells with uncorrectable hec byte error count register ? byte 2 (address = 0xn735) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received cells with uncorrectable hec byte error count[23:16] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 413 receive atm cell processor block ? receive atm cells with uncorrectable hec byte error count register ? byte 1 (address = 0xn736) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received cells with uncorrectable hec byte error count[15:8] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive atm cells with uncorrectable hec byte error count register ? byte 0 (address = 0xn737) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 received cells with uncorrectable hec byte error count[7:0] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 3. it will not correct the ?single-bit? error within th is particular atm cell. in fact, unless the receive atm cell processor block is configur ed otherwise, it will discard this particular atm cell. note: whenever the receive atm cell processor block discards atm cells for ?uncorrectable hec byte? errors it will also increment the ?receive atm cell processor block ? receive discarded atm cell count? registers. these registers are also 32-bit reset-upon-read registers t hat reside at address locations 0xn72c through 0xn72f. the bit format of these registers is presented below. receive atm cell processor block ? receive discarded atm cell count ? byte 3 (address = 0xn72c) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive ? discarded atm cell count[31:24] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive discarded atm cell count ? byte 2 (address = 0xn72d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive ? discarded atm cell count[23:16] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive discarded atm cell count ? byte 1 (address = 0xn72e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive ? discarded atm cell count[15:8] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm cell processor block ? receive discarded atm cell count ? byte 0 (address = 0xn72f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive ? discarded atm cell count[7:0]
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 414 rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 4. the hec byte verification block will remain in the ?detection? mode. how does the hec byte verification block tran sition back into the ?correction? state? the hec byte verification block will transition back into the ?correction? stat e once it has received ?m? consecutive cells with correct hec byte values. th is value for ?m? is also known as the ?correction threshold?. the user has the option to use the following values for ?m?: 1, 2, 4 and 8. the user can configure the receive atm cell processor block to use any of these values for ?m? by writing the appropriate value to the ?receive atm cell processor block ? re ceive atm control register ? byte 0?, as depicted below. receive atm cell processor block ? receive atm control register ? byte 0 (address = 0xn703) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 hec byte insert into udf1 enable hec status into udf2 enable hec byte correction threshold[1:0] receive utopia parity - odd unused descramble enable r/w r/w r/w r/w r/w r/o r/o r/w 1 1 x x 1 0 0 0 table 19 presents the relationship between the contents of the ?hec byte correction threshold[1:0]? bit-fields and the corresponding ?correction threshold? configured. table 19 the relationship between the contents of the ?hec byte correction threshold[1:0]? bit- fields the corresponding ?correction threshold? configured hec b yte c orrection t hreshold [1:0] r esulting ?c orrection t hreshold ? c onfigured (n umber of c ells ) 00 1 cell with no hec byte errors 01 2 consecutive cells with no hec byte errors 10 4 consecutive cells with no hec byte errors 11 8 consecutive cells with no hec byte errors 2.3.4.2 c ell p ayload d e -s crambler b lock after the ?hec byte verification? bloc k, the very next block within the sign al path (within the receive atm cell processor block) is the ?cell payload de-scrambler? block. figure 100 presents an illustration of the ?functional block diagram? of the receive atm cell processor block, with the ?cell payload de-scrambler? block highlighted. figure 100 illustration of the ?fun ctional block diagram? of the receive atm cell processor block with the ?cell payload de-scrambler? block highlighted
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 415 parity calculation block parity calculation block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte verification block hec byte verification block cell payload de-scrambler block cell payload de-scrambler block rxfifo rxfifo receive utopia interface block microprocessor interface block microprocessor interface block idle cell filter idle cell filter main data path from receive sts-3c/sts-12c poh processor block receive gfc nibble-field output i/f receive gfc nibble-field output i/f in numerous applications the payload portion of the in coming cells will scrambled by the remote terminal equipment. these cells are scrambled in order to prev ent the user data from mimicking framing or control bytes. therefore, the receive atm cell processor provides the user w ill the option of de-scrambling the payload of these cells in order to restore the original c ontent of the cell payload. (please note that this cell de- scrambler presumes that the cell payload were scrambled via the scra mbling generating polynomial of x 43 + 1.) the user can configure this op tion by setting bit 2 (de-scramble enable) within the ?receive atm cell processor ? receive atm control regi ster ? byte 0?, as depicted below. receive atm cell processor block ? receive atm control register ? byte 0 (address = 0xn703) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 hec byte insert into udf1 enable hec status into udf2 enable hec byte correction threshold[1:0] receive utopia parity - odd unused descramble enable r/w r/w r/w r/w r/w r/o r/o r/w 1 1 x x 1 0 0 1 2.3.4.3 i dle c ell f ilter idle cell filtering is actually achieved through the user of the receive user cell filter. as a consequence, we will now proceed to discuss the ?receive user cell filter?.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 416 2.3.4.4 t he r eceive u ser c ell f ilter b lock once a given atm cell has successfully passed throug h the ?hec byte verification? block, and has been processed by the ?cell de-scrambler? bl ock, it will now be processed by the ?receive user cell filter? block. figure 101 presents the functional block diagram of t he receive atm cell processor block with the ?receive user cell filter? block highlighted. figure 101 illustration of the ?receive atm cell processor? functional block diagram with the ?receive user-cell filter? block highlighted parity calculation block parity calculation block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte verification block hec byte verification block cell payload de-scrambler block cell payload de-scrambler block rxfifo rxfifo receive utopia interface block microprocessor interface block microprocessor interface block idle cell filter idle cell filter main data path from receive sts-3c/sts-12c poh processor block receive gfc nibble-field output i/f receive gfc nibble-field output i/f the receive atm cell processor block consists of four parallel user cell filters. these user cell filters are connected in parallel, in the sense that the entire ?re ceive? atm cell traffic will be presented to the inputs of each of the four ?user-cell? filters, at the same time. figure 102 attempts to clarify this phenomenon by presenting an illustration as to how each of these user cell filters is connected to the atm traffic.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 417 figure 102 an illustration of the co nfiguration of the four receive u ser cell filters within the receive atm cell processor block to parity calculation block user cell filter # 0 user cell filter # 0 user cell filter # 3 user cell filter # 3 user cell filter # 2 user cell filter # 2 user cell filter # 1 user cell filter # 1 to cell extraction memory from hec byte verification blocks each of these four (4) user cell filters can be configur ed to analyze all of the header bytes, within a given atm cell. based upon the value of these header bytes (wit hin a given cell), each of the four user cell filter blocks can be configured to perform either of the following functions. ? to filter (e.g., discard) the cell ? to not filter (e.g., permit the cell to pass through, along the data path) the cell ? to replicate (or copy) the cell, and route the replicate cell to the ?r eceive atm cell processor? block ? extraction processor block. ? to not replicate the cell. instructions on how to implement the following user cell filter options are presented below. ? enabling/disabling the user cell filter ? defining the user cell filter action ? defining the user cell filter sense ? specifying the user cell filter values
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 418 enabling/disabling the re ceive user cell filter the receive atm cell processor block permits the user to either enable or disable each of the four receive user cell filters. the user can accomplish this by wr iting the appropriate data into bit 3 (user cell filter enable), within the ?receive atm filter control ? byte 0? register; as depicted below. receive atm filter # 0, # 1, # 2, # 3 control ? byte 0 (address = 0xn743, 0xn753, 0xn763, 0xn773) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused user cell filter enable copy cell enable discard cell user cell filter sense r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 x 0 0 0 note: as the bit-format table for the ?receive atm filter control ? byte 0? register implies, each of the four (4) receive user cell filters can be individually enabled or disabled. further, each of these four receive user cell filters can be individually configured to either ?copy? or ?discard? cells (or both). setting this bit-field to ?1? enables the corresponding receiv e user cell filter. conver sely, setting this bit-field to ?0? disables the ?receive user cell filter?. if a given receive user cell filter is enabled, then it will perform action on all incoming atm cells, based upon the settings of the remaining register bits within this register; and that within both the ?receive atm filter control ? pattern? and ?receive atm filter control ? check? registers. conver sely, if the given receive user cell filter is disabled, then all user cells will pass through the receive user cell filter, and towards the ?parity calculation & insertion? block without any such actions performed on these cells. selecting the receive user cell filter action the receive atm cell processor block permits the user to specify the action that the user cell filter will take on each cell, that meets certain ?user-defined? filter ing requirements. the user can accomplish this by setting bits 2 (copy cell enable) and 1 (discard cell enable) , within the receive atm filter control ? byte 0? register; to the appropriate values. th ese two bit-fields are highlighted below. receive atm filter # 0, # 1, # 2, # 3 control ? byte 0 (address = 0xn743, 0xn753, 0xn763, 0xn773) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused user cell filter enable copy cell enable discard cell enable user cell filter sense r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 1 x x x bit 2 ? copy cell enable this bit-field permits the user to configure the ?rec eive user cell? filter (within the receive atm cell processor block) to either replicate (copy) or not re plicate a given cell that complies with the ?user-defined? filtering requirements. all copied cells are routed to the ?receive atm cell processor extraction memory?, where their contents can be read out by the user via the microprocessor interface. setting this bit-field to ?1? configures the receive user ce ll filter to copy all cells that comply with the ?user- cell? filter requirements, and to route these cells to the ?receive atm cell processor ? extraction memory?. conversely, setting this bit-field to ?0? configures the receive user cell filter to not copy these cells, and not route these cells to the ?receive atm cell processor ? extraction memory. bit 1 ? discard cell enable this bit-field permits the user to configure the ?rec eive user cell? filter (within the receive atm cell processor block) either discard or not discard a giv en cell that complies with t he ?user-defined? filtering
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 419 requirements. cells that are discarded will not be routed to the ?parity calculation and insertion? block. cells that are not discarded will proceed on through the remainder of the receive atm cell processor block circuitry (and rxfifo), for further processing. setting this bit-field to ?1? configures the receive user cell filter to discar d all cells that comply with the ?user- cell? filter requirements. conversely, setting this bit-field to ?0? configures the receive user cell filter to not discard the cells that comply with the ?user-cell? filter requirements. defining the user cell filter sense the sense of a given receive user cell filter is defined by the state of bit 0 (user cell filter sense) within the ?receive atm filter control ? byte 0? register; as described below. bit 0 - user cell filter sense receive atm filter # 0 , # 1, # 2, # 3 control ? byte 0 (address = 0xn743, 0xn753, 0xn763, 0xn773) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused user cell filter enable copy cell enable discard cell enable user cell filter sense r/o r/o r/o r/o r/w r/w r/w r/w 0 0 0 0 1 x x x this bit-field controls the ?filter mode? . if the user sets this bit-field to ?1? then the ?receive user-cell? filter will act, per the settings within bits 2 (copy cell enable) and 1 (discard cell enable) on cells with header byte patterns matching the ?user-cell? filtering criteria. c onversely, setting this bit-field to ?0? configures the ?receive user-cell? filter to act, per the settings within bits 2 (copy cell enable) and 1 (discard cell enable) on cells with header byte patterns not mat ching the ?user-cell? filtering criteria. specifying the receive user cell filtering criteria as described above, each of the four receive user ce ll filters (within the receive atm cell processor block) can be configured to perform a variety of actions (e.g., copy cells, discard cells, etc); based upon whether the header byte patterns of user cells match; or do not match a particular ?user-defined? filter criteria. the ?user-defined? filter criteria (for each of the four receive user cell filter blocks, within the receive atm cell processor block) are ultimately defined by the values re siding within a total of eight (8) registers. four of these registers are referred to as ?user cell filter ? pattern? registers; and the remaining four registers are referred to as ?user cell filter ? check? registers. each of these register types are defined below. receive user cell filter ? pattern registers the four user cell filter ? pattern registers permit the user to specify the header byte pattern for the receive user cell filter. there are four user cell filt er ? pattern registers (one for each of the four (4) header bytes, within an atm cell). the bit-format of t hese ?user cell filter ? pattern registers? is presented below. receive atm filter # 0, # 1, # 2, # 3 pattern ? header byte 1 (address = 0xn744, 0xn754, 0xn764, 0xn774) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter pattern ? header byte 1[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 420 receive atm filter # 0, # 1, # 2, # 3 pattern ? header byte 2 (address = 0xn745, 0xn755, 0xn765, 0xn775) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter pattern ? header byte 2[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive atm filter # 0, # 1, # 2, # 3 pattern ? header byte 3 (address = 0xn746, 0xn756, 0xn766, 0xn776) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter pattern ? header byte 3[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive atm filter # 0, # 1, # 2, # 3 pattern ? header byte 4 (address = 0xn747, 0xn757, 0xn767, 0xn777) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter pattern ? header byte 4[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 note: each of the four receive user cell filters (within the receive atm cell proc essor block) contains their own set of ?user cell filter ? pattern? registers. receive user cell filter ? check registers the four user cell filter ? check registers permit the us er to specify which bits (within the header bytes of user cells) will be checked and comp ared with the contents of the ?user cell filter ? pattern registers?. there are four (4) ?user cell filter-check? registers (one for each of the four header bytes within an atm cell). setting a particular bit-field to ?0? configures the ?receive user cell filter? to not compare the corresponding bit-field (within the header bytes of the incoming user cell) to the corresponding bit-value, within the user cell filter ? pattern register; during user cell pattern checking. conversely, setting a particular bit-field to ?1? configures the ?receive user cell filter? to compare the corresponding bit-field (within the header bytes of the incoming user cell) to the corresponding bit-value, within the user cell filter ? pattern register; during user cell pattern checking. for example, if the user were write the value ?0x00? in to a given ?user cell filter ? check register?, then the receive user cell filter will not check and compare t he value of the corresponding header byte, within an incoming user cell; to the contents of the corresponding ?u ser cell filter ? pattern? register during user cell pattern checking. conversely, if the user were to writ e the value ?0xff? into a given ?user cell filter ? check register?, then the user cell filter will check and compare all eight bits (within the corresponding byte) within an incoming user cell; to the content s of the corresponding ?user cell filter ? pattern? register during user cell pattern checking. the bit-format of the four ?user cell filt er ? check registers? is presented below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 421 receive atm filter # 0, # 1, # 2, # 3 check ? header byte 1 (address = 0xn748, 0xn758, 0xn768, 0xn778) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter check ? header byte 1[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive atm filter # 0, # 1, # 2, # 3 check ? header byte 2 (address = 0xn749, 0xn759, 0xn769, 0xn779) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter check ? header byte 2[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive atm filter # 0, # 1, # 2, # 3 check ? header byte 3 (address = 0xn74a, 0xn75a, 0xn76a, 0xn77a) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter check ? header byte 3[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 receive atm filter # 0, # 1, # 2, # 3 check ? header byte 4 (address = 0xn74b, 0xn75b, 0xn76b, 0xn77b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 user cell filter check ? header byte 4[7:0] r/w r/w r/w r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 note: each of the four user cell filters (within the receive at m cell processor block) contains their own set of ?user cell filter ? check? registers. counting filtered cells the user can keep account of the number of user cells that have been filtered out by the receive user cell filter by periodically reading out the contents of the ?receive atm filter co unt? registers. each time a user cell is filtered (e.g., either discarded or copied) by th e ?receive user cell? filter, then this counter will be incremented by the value of ?1?. this counter will increment until it reaches the value of 0xffffffff. at this time, the counter will ?saturate? and will not increment any further until read. these registers are 32 bits, in width and are ?reset-upon-read. the bi t-format for these regi sters (for each of t he four filters) is presented below. receive atm filter # 0, # 1, # 2, # 3 ? filtered cell counter ? byte 3 (address = 0xn74c, 0xn75c, 0xn76c, 0xn77c) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 filtered cell count[31:24]
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 422 rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm filter # 0, # 1, # 2, # 3 ? filtered cell counter ? byte 2 (address = 0xn74d, 0xn75d, 0xn76d, 0xn77d) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 filtered cell count[23:16] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm filter # 0, # 1, # 2, # 3 ? filtered cell counter ? byte 1 (address = 0xn74e, 0xn75e, 0xn76e, 0xn77e) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 filtered cell count[15:8] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 receive atm filter # 0, # 1, # 2, # 3 ? filtered cell counter ? byte 0 (address = 0xn74f, 0xn75f, 0xn76f, 0xn77f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 filtered cell count[7:0] rur rur rur rur rur rur rur rur 0 0 0 0 0 0 0 0 each of the four user cell filters (within the receiv e atm cell processor block) contains their own set of ?filtered cell counter? registers. the procedure for reading out the contents of the receive atm filter ? filtered cell counter register in order to properly read out the contents of these r egisters, the user must read these registers in the following order. ? receive atm filter #0, #1, #2, #3 ? filtered cell co unter ? byte 3 (address = 0xn74c, 0xn75c, 0xn76c, 0xn77c) ? receive atm filter #0, #1, #2, #3 ? filtered cell co unter ? byte 2 (address = 0xn74d, 0xn75d, 0xn76d, 0xn77d) ? receive atm filter #0, #1, #2, #3 ? filtered cell counter ? byte 1 (address = 0xn74e, 0xn75e, 0xn76e, 0xn77e) ? receive atm filter #0, #1, #2, #3 ? filtered cell counter ? byte 0 (address = 0xn74f, 0xn75f, 0xn76f, 0xn77f)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 423 2.3.4.5 t he r eceive c ell e xtraction p rocessor the receive atm cell processor block consists of a ?rec eive cell extraction buffer/processor? block. figure 103 presents the functional block diag ram of the ?receive atm cell processor block with the ?receive cell extraction buffer/processor? block highlighted. figure 103 illustration of the receive atm cell pro cessor block functional block diagram, with the ?receive cell extraction buffer/processor? block highlighted parity calculation block parity calculation block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte verification block hec byte verification block cell payload de-scrambler block cell payload de-scrambler block rxfifo rxfifo receive utopia interface block microprocessor interface block microprocessor interface block idle cell filter idle cell filter main data path from receive sts-3c/sts-12c poh processor block receive gfc nibble-field output i/f receive gfc nibble-field output i/f the receive cell extraction buffer/pr ocessor block permits the user to read out the contents of an ?inbound? atm cell via the microprocessor interface. if the user configures the ?receive user cell filter? appropriately, the ?receive user cell filter? will copy (e.g., replicate) the contents of ce rtain cells (which comply with the user cell filtering requirements). these copied cells will be routed to the ?receive cell extraction buffer/processor? block where it can be read out and processed by the microprocessor interface. the format of the atm cell that is read fr om the ?receive cell extraction? buffer as the user reads out the contents of an atm cell fr om the ?receive cell extraction? buffer (via the microprocessor interface), they will be expected to read this atm cell data via a 32-bit wide register/buffer interface. as a consequence, the user must read out 56 byte size atm cells from the ?receive cell extraction? buffer. the byte format of th is 56-byte atm cell is as illustrated below. figure 104 byte format of the atm cells that are read out from the ?receive cell extraction? memory
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 424 header bytes (4 bytes) hec byte (1 byte) user defined field (3 bytes) cell payload bytes (48 bytes) as a consequence, the user must read out a total of 14 ?32-bit? words from the ?receive cell extraction? buffer for each atm cell that is read ou t of the receive cell extraction buffer. procedure for reading a cell from the ?receive cell extraction buffer? the user can read an atm cell from the ?transmit cell extraction buffer? within the transmit atm cell processor block, by exec uting the following steps. step 1 ? flush the contents of the ?receive cell extraction buffer? this is accomplished by executing a ?transmit cell extraction buffer? reset. the user can perform this ?cell extraction buffer? reset by doing the following. step 1a ? write a ?0? into bit 4 (extraction memory reset*) within the ?transmit atm cell ? memory control? register; as depicted below. receive atm cell ? memory control register (address = 0xn713) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1->0 0 1 1 0 step 1b ? write a ?1? into bit 4 (extraction memory reset*), within the ?receive atm cell ? memory control? register; as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 425 receive atm cell ? memory control register (address = 0xn713) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0->1 0 1 1 0 note: this step should typically be performed upon power-up, prior to processing any atm cell traffic through the xrt94l33. this step is not necessary after the first ce ll has been read from the ?receive cell extraction buffer? following a pow er cycle to the chip. step 2 ? check and see if an atm cell exists in the ?receive cell extraction buffer? this can be accomplished by one of two approaches. ? polling approach ? interrupt-driven approach each of these approaches is described below. executing step 2 using the polling approach the user can determine whether or not a cell is avail able, within the ?receive cell extraction buffer? by testing the state of bit 3 (extracti on memory clav) within the receive atm cell ? memory control register; as depicted below. receive atm cell ? memory control register (address = 0xn713) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1 x 1 1 0 if bit 3 is set to ?1?, then the ?receive cell extracti on buffer? contains an atm cell that needs to be read. at this point, the user should proceed on to step 3. conversely, if bit 3 is set to ?0?, then the ?receive cell extraction buffer? does not contain an atm cell that needs to be read. at this point, the microprocessor interf ace should continue to poll the state of this bit-field and wait until this bit-field toggles to ?1?. executing step 2 using the interrupt-driven approach in order to reduce or eliminate the microprocessor overhea d of continuously polling the state of bit 3, the user can use the ?receive cell extraction? interrupt feature, within the chip. if the microprocessor invokes this feature, then the xrt94l33 will generate an interrupt anytime a new cell has been received and loaded into the ?receive cell extraction buffer?. the user can enable the ?cell extraction? interrupt by setti ng bit 5 (cell extraction interrupt enable), within the ?receive atm cell processor ? interrupt enable? register to ?1? as indicated below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 426 receive atm cell processor ? interrupt enable register (address = 0xn70f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt enable cell insertion interrupt enable cell extraction memory overflow interrupt enable cell insertion memory overflow interrupt enable detection of hec byte error interrupt enable detection of parity error interrupt enable r/o r/o r/w r/w r/w r/w r/w r/w 0 0 1 0 0 0 0 0 once the ?cell extraction buffer? receives a ?copied? cell from the ?receive user cell filter?, then the xrt94l33 will do all of the following: ? it will toggle the ?int*? output pin ?low?. ? it will set bit 5 (cell extraction interrupt status) wi thin the receive atm cell pr ocessor ? interrupt status register, to ?1? as depicted below. receive atm cell processor ? interrupt status register (address = 0xn70b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt status cell insertion interrupt status cell extraction memory overflow interrupt status cell insertion memory overflow interrupt status detection of hec byte error interrupt status detection of parity error interrupt status r/o r/o rur rur rur rur rur rur 0 0 1 0 0 0 0 0 at this point, the user can now proceed onto step 3. step 3 ? read out the very first 32-bit word of this new atm cell from the ?receive cell extraction buffer?. this is accomplished by executin g the following four sub-steps. step 3a ? read the contents of the first byte (of this newly received atm cell) from the ?receive atm cell ? insertion/extraction memory register ? byte 3; as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 427 receive atm cell ? insertion/extraction memory register ? byte 3 (address = 0xn714) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[31:24] r/w r/w r/w r/w r/w r/w r/w r/w a7 a6 a5 a4 a3 a2 a1 a0 note: in this case, the contents of the first byte (within this atm cell) is of the value [a7, a6, a5, a4, a3, a2, a1, a0] step 3b ? read the contents of the second byte (of this new atm cell) from the receive atm cell ? insertion/extraction memory register ? byte 2; as depicted below. receive atm cell ? insertion/extraction memory register ? byte 2 (address = 0xn715) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[23:16] r/w r/w r/w r/w r/w r/w r/w r/w b7 b6 b5 b4 b3 b2 b1 b0 note: in this case, the contents of the second byte (within this atm cell) is of the value [b7, b6, b5, b4, b3 , b2, b1, b0] step 3c ? read the contents of the third byte (of this new atm cell) from the receive atm cell ? insertion/extraction memory register ? byte 1; as depicted below. receive atm cell ? insertion/extraction memory register ? byte 2 (address = 0xn716) bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 insertion/extraction memory data[15:8] r/w r/w r/w r/w r/w r/w r/w r/w c7 c6 c5 c4 c3 c2 c1 c0 note: in this case, the contents of the second byte (within this atm cell) is of the value [c7, c6, c5, c4, c3, c2, c1, c0] step 3d ? read the contents of the fourth byte (of this new atm cell) from the receive atm cell ? insertion/extraction memory register ? byte 0; as depicted below. receive atm cell ? insertion/extraction memory register ? byte 2 (address = 0xn717) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[7:0] r/w r/w r/w r/w r/w r/w r/w r/w d7 d6 d5 d4 d3 d2 d1 d0 note: in this case, the contents of the second byte (within this atm cell) is of the value [d7, d6, d5, d4, d3, d2, d1, d0] step 4 ? continue to read out the contents of the remaining bytes of this atm cell from the ?receive cell extraction memory?. this is accomplished by executin g the procedure, outlined in step 3, repeatedly for 13 more times.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 428 2.3.4.6 4t he r eceive c ell i nsertion b uffer /p rocessor the receive atm cell processor block consist of a ?receive cell insertion buffer/processor? block. figure 105_ presents the functional block diagram of the receive atm cell processor block with the receive cell insertion buffer/processor? block highlighted. figure 105 illustration of the receive atm cell pro cessor block functional block diagram, with the ?receive cell insertion buffer/processor? block highlighted parity calculation block parity calculation block user cell filter block user cell filter block cell extraction buffer/ processor cell extraction buffer/ processor cell insertion buffer/ processor cell insertion buffer/ processor hec byte verification block hec byte verification block cell payload de-scrambler block cell payload de-scrambler block rxfifo rxfifo receive utopia interface block microprocessor interface block microprocessor interface block idle cell filter idle cell filter main data path from receive sts-3c/sts-12c poh processor block receive gfc nibble-field output i/f receive gfc nibble-field output i/f the receive cell insertion buffer/processor block permits the user to load the co ntents of an ?outbound? atm cell into the ?receive cell insertion buffer? via the microp rocessor interface. once this cell has been loaded into the ?receive cell insertion buffer?, then it will be transmitted to the ?rxfifo? where it will ultimately wait to be read out of the receive utopia interface block via the atm layer processor block. this feature can be very useful for debugging and diagnostic s on the ?utopia? side of the chip. the format of atm cell data that is written into the ?receive cell insertion? buffer as the user loads the contents of an atm cell into the ?r eceive cell insertion? buffe r (via the microprocessor interface), they will be expected to writ e this atm cell data into a 32 bit wide register/buffer interface. as a consequence, the user must write in 56-byte size at m cells into the ?receive cell insertion? buffer. the byte format of this 56 byte atm ce ll is as illustrated below in figure 106. figure 106 byte-format of the atm cell that is to be loaded into the ?receive cell insertion? memory
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 429 header bytes (4 bytes) hec byte (1 byte) user defined field (3 bytes) cell payload bytes (48 bytes) as a consequence, the user must write in a total of 14 ?32-bit words? into the ?receive cell insertion? buffer for each atm cell that is written into the ?receive cell insertion? buffer. procedure for writing a cell into the ?receive cell insertion buffer? the user can write an atm cell into the ?receive cell insertion buffer? within the receive atm cell processor block, by executing the following steps. step 1 ? flush the contents of the ?receive cell insertion buffer? this is accomplished by executing a ?receive cell insertion buffer? r eset. the user can perform this ?transmit cell insertion buffer? reset by doing the following. step 1a ? write a ?0? into bit 2 (insertion memory reset*), within the ?receive atm cell ? memory control? register; as depicted below. receive atm cell ? memory control register (address = 0xn713) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1 0 1->0 1 0 step 1b ? write a ?1? into bit 2 (insertion memory reset*), within the ?receive atm cell ? memory control? register; as depicted below. receive atm cell ? memory control register (address = 0xn713)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 430 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1 0 0->1 1 0 note: this step should typically be performed upon power-up, pr ior to writing in any atm cell data into the ?receive cell insertion buffer?. this step is not necessary after the first cell has been written into the ?receive cell insertion buffer? following a power cycle to the chip. step 2 ? check and verify that there is sufficient space available (within the receive cell insertion buffer) to handle this cell. this can be accomplished by one of two approaches. ? polling approach ? interrupt-driven approach. each of these approaches is described below. executing step 2 using the polling approach the user can determine whether or not there is room (to write another atm cell of data) in to the ?receive cell insertion? buffer? by polling the state of bit 1 (insertion memory room) within the ?receive atm cell ? memory control register? as depicted below. receive atm cell ? memory control register (address = 0xn713) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1 0 1 x 0 if bit 1 (insertion memory room) is set to ?1? then the ?receive cell insertion buffer? is not too full to accept another cell. at this point, the micr oprocessor can now move onto step 3. conversely, if bit 1 is set to ?0? then the ?receive cell insertion buffer? is too full to accept another cell. the microprocessor interface should continue to poll the state of this bit-fiel d and wait until this bit-field toggles to ?1?. executing step 2 using the interrupt-driven approach in order to reduce or eliminate the microprocessor overhea d of continuously polling the state of bit 1, the user can use the ?receive cell insertion? interrupt feature, within the chip. if the microprocessor invokes this feature, then the xrt94l33 will generate an interrupt any time a cell (residing in the receive cell insertion buffer) has been inserted into the ?receive input data path? (thereby freeing up some space within the receive cell insertion buffer). the user can enable the ?receive cell insertion? interr upt by setting bit 4 (cell insertion interrupt enable), within the ?receive atm cell processor ? interrupt enable? register to ?1? as indicated below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 431 receive atm cell processor ? interrupt enable register (address = 0xn70f) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt enable cell insertion interrupt enable cell extraction memory overflow interrupt enable cell insertion memory overflow interrupt enable detection of hec byte error interrupt enable detection of parity error interrupt enable r/o r/o r/w r/w r/w r/w r/w r/w 0 0 0 1 0 0 0 0 once a cell (residing within the receive cell insertion buffer) has been inserted into the ?receive input data path?, then the xrt94l33 will do all of the following: ? it will toggle the ?int*? output pin ?low?. ? it will set bit 4 (cell insertion in terrupt status), within the receive atm cell proces sor ? interrupt status register; to ?1? as depicted below. receive atm cell processor ? interrupt status register (address = 0xn70b) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused cell extraction interrupt status cell insertion interrupt status cell extraction memory overflow interrupt status cell insertion memory overflow interrupt status detection of hec byte error interrupt status detection of parity error interrupt status r/o r/o rur rur rur rur rur rur 0 0 0 1 0 0 0 0 at this point, the user can now proceed on with step 3. step 3 ? inform the ?receive cell insertion processor? that the very next 32-bit word to be written into the ?receive cell insertion buffer? is the first word of a new atm cell. this is accomplished by writing the value ?1? into bi t 0 (insertion memory write soc), within the ?receive atm cell ? memory control r egister? as depicted below. receive atm cell ? memory control register (address = 0xn713) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1 0 1 1 1 step 4 ? write the very first 32-bit word of this new atm cell into the ?receive cell insertion buffer?. this is accomplished by executin g the following four sub-steps. step 4a - write the contents of first byte (of this new atm cell) into the receive atm cell ? insertion/extraction memory register ? byte 3; as depicted below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 432 receive atm cell ? insertion/extraction memory register ? byte 3 (address = 0xn714) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[31:24] r/w r/w r/w r/w r/w r/w r/w r/w a7 a6 a5 a4 a3 a2 a1 a0 note: in this case, the contents of the first byte (within this atm cell) is of the value [a7, a6, a5, a4, a3, a2, a1, a0] step 4b ? write the contents of the second byte (of this new atm cell) into the receive atm cell ? insertion/extraction memory register ? byte 2; as depicted below. receive atm cell ? insertion/extraction memory register ? byte 2 (address = 0xn715) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[23:16] r/w r/w r/w r/w r/w r/w r/w r/w b7 b6 b5 b4 b3 b2 b1 b0 note: in this case, the contents of the second byte (within this atm cell) is of the value [b7, b6, b5, b4, b3 , b2, b1, b0] step 4c ? write the contents of the third byte (of this new atm cell) into the receive atm cell ? insertion/extraction memory register ? byte 1; as depicted below. receive atm cell ? insertion/extraction memory register ? byte 2 (address = 0xn716) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[15:8] r/w r/w r/w r/w r/w r/w r/w r/w c7 c6 c5 c4 c3 c2 c1 c0 note: in this case, the contents of the second byte (within this atm cell) is of the value [c7, c6, c5, c4, c3, c2, c1, c0] step 4d ? write the contents of the fourth byte (of this new atm cell) into the receive atm cell ? insertion/extraction memory register ? byte 0; as depicted below. receive atm cell ? insertion/extraction memory register ? byte 2 (address = 0xn717) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 insertion/extraction memory data[7:0] r/w r/w r/w r/w r/w r/w r/w r/w d7 d6 d5 d4 d3 d2 d1 d0 note: in this case, the contents of the second byte (within this atm cell) is of the value [d7, d6, d5, d4, d3, d2, d1, d0] step 5 ? inform the ?cell insertion processor? that the very next 32-bit word to be written into the ?cell insertion buffer? is not th e first word of a new atm cell. this is accomplished by writing the value ?0? into bi t 0 (insertion memory write soc), within the ?receive atm cell ? memory control r egister? as depicted below.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 433 receive atm cell ? memory control register (address = 0xn713) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused extraction memory reset* extraction memory clav insertion memory reset* insertion memory room insertion memory write soc r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 1 0 1 1 0 step 6 ? continue to write the contents of the remain ing bytes of this atm cell into the ?cell insertion memory?. this is accomplished by executing the procedur e, outlined in step 4, repeatedly for 13 times. notes: as the user writes the contents of an atm cell into the ?r eceive cell insertion memory? t hey must follow the mandated atm cell byte format, as depicted in figure 106. if the user performs a read operation to the ?receive atm cell ? insertion/extraction memory register ? bytes 3 through 0? they will not be reading out the contents of the receive cell insertion buffer. instead, the user will be reading out data from the ?receive cell extraction? buffer. 2.3.4.7 t he r eceive gfc n ibble -f ield s erial o utput p ort the first four bit-field of each cell header are the gfc bits. the receive cell processor will output the contents of the gfc nibble-field for each cell that it re ceives, via the ?gfc nibble field? serial output port. the ?receive gfc nibble-field? serial output port consists of the following pins. ? rxgfc ? rxgfcclk ? rxgfcmsb the data is output via the rxgfc output pin. the order of transmission, within a given cell, is with the msb first and in descending order until transmitting the lsb bit. afterwards, the ?gfc nibb le-field? serial output port will output the msb for the gfc nibble-field of the nex t cell. this data is clocked out on the rising edge of the rxgfcclk output signal. t he rxgfcmsb output pin will be pulsed ?high? each time the msb of the gfc nibble field, for a given cell, is present at the rxgfc input. figur e 107 presents an illustration depicting the behavior of the rxgfc serial output port signals. figure 107 illustration of the behavior of the rxgfc serial output port signals
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 434 rxgfcclk rxgfcmsb t52 rxgfc bit 3 bit 2 bit 1 bit 0 t50 t48 t51 t47 t49 4.3.4.8 receive atm cell pr ocessor block interrupts ? cell delineation ? hec byte verification ? idle cell filtering (optional) ? user/oam cell filtering (optional) ? cell-payload de-scrambling (optional) the receive atm cell processor will also output t he gfc nibble value of each incoming cell, via the ?receive gfc nibble field? serial output port. figure 108 presents a simple block diagram of the rece ive atm cell processor block along with its external pins. figure 108 simple illustration of the receive at m cell processor, with associated pins
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 435 receive atm cell processor block rxcelltxed rxgfcclk rxgfcmsb rxgfc from receive utopia interface block from receive sts-3c/sts-12c poh processor block 2.3.4.8 7.3.2.8 r eceive atm c ell p rocessor i nterrupts the receive cell processor will generate interrupts upon ? hec errors ? oam cell received ? loss of cell delineation if one of these conditions occur, and if that particular condition is enabled for interrupt generation, then when the local c/ p reads the uni interrupt stat us register, as shown below, it should read ?1xxxxxxxb? (where the -b suffix denotes a binary expression, and ?x? denotes a ?don?t care? value). operation block interrupt status register ? byte 0 (address = 0x0113) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 receive atm cell processor block interrupt status receive sts-3 toh block interrupt status receive sonet/vc-3 poh block interrupt status receive ppp processor block interrupt status transmit atm cell processor block interrupt status unused transmit ppp processor block interrupt status r/o r/o r/o r/o r /o r/o r/o r/o 1 0 0 0 0 0 0 0 at this point, the local c/ p will have determined that the receive cell processor block is the source of the interrupt, and that the interrupt servic e routine should branch accordingly. in order to accomplish this the local c/ p should now read the ?rx cp interrupt status regist er? (address = 0x0113). t he bit format of this register is presented below.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 436 cell delineation algorithm hec byte verification coset polynomial correction mode detection mode idle cell filtering user cell filtering descrambling gfc (generic flow control) extraction oam cell support and reception interrupt support for the receive cell processor block 2.3.5 the receive utopia interface block the receive utopia interface block complies with ?utopia level 1, 2 and 3? compliant interface to interconnect the uni chip to atm layer or atm ad aptation layer processors, operating up to 800 mbps. additionally, the xrt94l33 provides the user with the opt ion of varying the following features associated with the receive utopia bus interface. ? operating the utopia data bus per the utopia levels 1, 2 and 3 standards ? transmit utopia data bus width of 8 or 16 bits ? the cell size (e.g., the number of octets being processed per cell via the utopia bus) ? whether the receive utopia clock de-skewing pll is enabled or not. figure 109 presents a simplistic illustrat ion of the receive utopia interfac e block, along with its external output pins. figure 109 a simple illustration of the receive utopia interface block a discussion of the operation of the receive utopia bus interface along with each of these options will be presented below. the pins of the receive utopia bus interface the atm layer processor will interf ace to the receive utopia interf ace block via the following pins. ? rxudata[15:0] - receive utopia data bus input pins ? rxuaddr[4:0] - receive utopia address bus input pins ? rxuclk receive utopia interface block clock input pin ? rxuclko receive utopia interface block clock output pin ? rxusoc receive ?start of cell? indicator input pin ? rxuprty receive utopia ? odd parity output pin ? rxuenb* receive utopia data bus ? read enable input pin
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 437 ? rxuclav/rfullb* rxfifo cell available
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 438 rxudata[15:0] - receive utopia data bus outputs the atm layer processor will read atm cell data from t he receive utopia interface block in a byte-wide (or word-wide) manner, via these output pins. the rece ive utopia data bus can be configured to operate in the ?8 bit wide? or ?16 bit wide? mode (see section _) . if the ?8-bit wide? mode is selected, then only the rxudata[7:0] output pins will be active and capable of transmitting data. if the 16-bit wide mode is selected, then all 16 output pins (e.g., rxudata[15:0]) will be acti ve. the receive utopia data bus is tri-stated while the active low rxuenb* (receive utopia bus - output enable) input signal is ?h igh?. therefore, the atm layer processor must assert this signal (e.g., toggle rxuenb* low) in order to read the atm cell data from the receive utopia interface block. the data on th e receive utopia data bus output pins are updated on the rising edge of the receive utopia interface block clock signal, rxuclk. rxuaddr[4:0] - receive utopia address bus inputs these input pins are used only when the uni is operat ing in the multi-phy mode. therefore, for more information on the receive utopia a ddress bus, please see section _. rxuclk - receive utopia interface block - clock signal input pin the receive utopia interface block uses this signal to update the data on the receive utopia data bus. the receive utopia interface block also uses this signal to sample and latch the data on the receive utopia address bus pins (during multi-phy operation), into the receive utopia in terface block circuitry. this clock signal can run at frequenci es of 25 mhz, 33 mhz, or 50 mhz. rxuclko ? receive utopia interface block clock output signal if the ?receive utopia clock de-skewing? pll is e nabled, then the atm layer processor can use to this signal to sample the contents of the ?outbound? atm cell s, as well as to when to assert the utopia address (during multi-phy operation). similar to the ?rxuclk? signal, this signal can run at frequencies up to 50mhz. rxuenb* - receive utopia data bus - output enable input the receive utopia data bus is tri-stated while this input signal is negated. therefore, the atm layer processor must assert this ?active-lo w? signal (toggle it ?low?) in order to read the byte (or word) from the receive utopia interface block vi a the receive utopia data bus. rxuprty - receive utopia - odd parity bit output pin the receive utopia interface block will compute the odd -parity of each byte (or word) of atm cell data that it will place on the receive utopia data bus. the receive utopia data bus w ill output the value of the computed parity bit at the rxuprty output pin, whil e the corresponding byte (or word) is present on the receive utopia data bus. this features allows the atm layer processor to perform parity checking on the data that it receives from the receive utopia interface block. rxusoc - receive utopia - ?start of cell? indicator output pin the receive utopia interface block will pulse this out put signal ?high?, for one clock period of rxuclk, when the first byte (or word) of a new atm cell is present on the receive utopia data bus. this signal will be ?low? at all other times. rxuclav/rxemptyb* - rx fifo cell available/rxempty* this output signal is used to alert the atm layer proc essor that the rx fifo contains some atm cell data that is available for reading. please see section _ for more information regarding this signal. s electing the utopia l evel the xrt94l33 permits the user to configure the receive utopia interface block in either of the following ?utopia levels?. ? utopia level 3
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 439 ? utopia level 1 or 2 the user can configure the receive utopia interf ace block (within the xrt94l33) to operate in the appropriate utopia level, by writin g the appropriate value into bit 7 (utopia level) within the ?receive utopia control register?, as depicted below. receive utopia control register ? byte 0, address = 0x0403 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level multi-phy mode back-to-back polling enable direct status access receive utopia data bus width[1:0] cell_size_sel[1:0] r/w r/w r/w r/w r/w r/w r/w r/w x 0 0 0 x x 1 1 setting this bit-field to ?0? configures the receive utopia interface block to support ?utopia level 3? signaling. conversely, setting this bit-field to ?1? co nfigures the receive utopia interface block to support the ?utopia levels 1 and 2? form of signaling. a description of the operati on of the receive utopia interface block, for utopia level 1, 2 and 3 operation is presented below. utopia level 1 and 2 operation utopia level 3 operation s electing the utopia d ata b us w idth the utopia data bus width can be selected to be either 8 or 16 bits by writing the appropriate data into bits 3 and 2 (receive utopia data bus wi dth[1:0]) within the ?receive utopia control? register, as depicted below. receive utopia control register ? byte 0, address = 0x0403 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level multi-phy mode back-to-back polling enable direct status access receive utopia data bus width[1:0] cell_size_sel[1:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 0 0 0 x x 1 1 if the user chooses a utopia data bus width of 8 bits, then only the receive utopia data outputs: rxudata[15:8] will be active. (the output pins: rx udata[7:0] will not be active). if the user chooses a utopia data bus width of 16 bits, then all of the rece ive utopia data output: rxudata[15:0] will be active. the following table relates the value of bits 2 and 3 (receive utopia data bus width[1:0]) within the receive utopia control register, to the co rresponding width of the utopia data bus. table 20 the relationship between the contents of ?receive utopia data bus width[1:0] within the receive utopia control register and the operating width of the utopia data bus r eceive utopia d ata b us w idth [1:0] w idth of utopia d ata b us 00 in-active: 01 8 bits 10 16 bits 11 not valid (do not use)
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 440 selecting the cell size (number of octets per cell) the xrt94l33 permits the user to select the number of octets per cell that the receive utopia interface block will process. specifically, the user has the following cell size options. ? if the utopia data bus width is set to 8 bits then the user can choose: 52 bytes (with no hec byte in the cell), or 53 bytes (with either a dummy or actual hec byte in the cell) ? if the utopia data bus width is set to 16 bits, then the user can choose: 52 bytes (with no hec byte in the cell), or 54 bytes (with either a dummy or actual hec byte, and a stuff byte in the cell) the user makes his/her selection by writing the appropriate data into bits 1 and 0 (cell_size_sel[1:0]) within the receive utopia control re gister, as depicted below. receive utopia control register ? byte 0, address = 0x0403 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level multi-phy mode back-to-back polling enable direct status access receive utopia data bus width[1:0] cell_size_sel[1:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 0 0 0 1 1 x x the following table presents the relationship between the value of this bit and the number of octets/cell that the receive utopia interf ace block will process. table 21 the relationship between the contents of bits 1 and 0 (cell_size_sel[1:0]) within the transmit utopia control register, and the number of octets per cell that will be processed by the transmit utopia interface blocks per assertion of txusoc c ell _s ize _s el [1:0] n umber of b ytes /c ells 00 52 bytes/cell 01 53 bytes/cell (only value if the transmit utopia data bus width = 8 bits) 10 54 bytes/cell 11 unused once the user has implemented his/her selection for t he cell size, then the receive utopia interface block will be configured to process the ?cell si ze? number of octets per cell. cell level handshaking atm forum documentation refers to both ?cell level ? and ?octet-level? handshaking. however, the xrt94l33 only supports the ?cell-level? handshaking mode . octet-level handshaking is not supported. in the ?cell-level? handshaking mode, w hen the rxuclav output is at a logic ?1?, it means that the rx fifo contains at least one complete atm cell of data that is available for reading by the atm layer processor. when rxuclav toggles from ?high? to ?low?, it indicate s that rx fifo contains less than one complete atm cell. the atm layer processor is expected to monito r the rxuclav output, and quickly respond and read the rx fifo, whenever the rxuclav output signal is asserted. figure 110 presents a timing diagram that illustrates t he behavior of various receive utopia interface block signals, when the receive utopia interface block is operating in the ?cell- level? handshaking mode.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 441 figure 110 the uni can operate in either the ?octet-level? or ?cell-level? handshake mode, when operating in the single-phy mode. however, only the cell-level handshake mode is available when the uni is operating in the multi-phy mode. for more information on single phy and multi phy operation, please see section _. the user can configure the uni to operate in one of these two handshake modes by writing the appropriate data to bit 5 (handshake mode) of the utop ia configuration register, as depicted below. this interface supports both an 8 and 16 bit wide data bus. since data is received at clock rates independent of the atm layer clock rate, the received cell data is written into an internal fifo by the receive cell processor block. this fifo will be referred to as th e rx fifo throughout this document. the receive cell processor will delineate, c heck for hec byte errors, filter and de-scr amble atm cells. whatever cells were not discarded, by the receive cell pr ocessor, will be written into the rx fifo, where it can be read out from the uni device, by the atm layer processor. the re ceive utopia interface block will inform the atm layer processor that it has cell dat a available for reading, by asserti ng the rxuclav pin ?high?. figure 111 presents a simple illustration of the receive utop ia interface block and the associated pins. figure 111 simple block diagram of receive utopia block of uni receive utopia interface rxuclk rxuenb rxuprty rxudata[15:0] rxusoc rxuclav/rxemptyb* rxuaddr[4:0] from receive atm cell processor detailed functional description of receive utopia the purposes of the receive utopia interface block are to: ? receive filtered atm cell data from the receive cell processor and make this data available to the aal or atm layer processor. ? inform the atm layer processor whenever the rxfifo contains cell data that needs to be read. ? inform the atm layer processor that it has no more cell data to be read.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 442 ? compute and present the odd-parity value of the byte (or word) that is present at the receive utopia data bus. ? indicate the boundaries of cells, to the atm layer processor, by pulsing the rxusoc (receive start of cell) pin each time the first byte (or word) of a new cell is present on the receive utopia data bus. the receive utopia interface block co nsists of the following sub-blocks: ? receive utopia output interface ? receive utopia cell fifo (rx fifo) ? receive utopia fifo manager the receive utopia interface block consists of an output interface complying to the ?utopia level 2 interface specifications?, and the rxfifo. the width of the receive utopia data bus is user-configurable to be either 8 or 16 bits. the receive utopia inte rface block also allows the atm layer processor to perform parity checking on all data t hat it receives from it (the receiv e utopia interface block), over the receive utopia data bus. the receive utopia interf ace block computes the odd-parity of each byte (or word) that it will place on the receive utopia data bus. the receive utopia interface block will then output the value of this computed parity at the rxprty pin, while the corresponding data byte (word) is present at the rxdata[15:0] output pins. the receive utopia interface block can be configured to process 52, 53, and 54 bytes per cell; and will assert the rxusoc (receive ?start of cell?) output pin at the cell boundaries. if the receive utopia interface block detects a ?runt? cell (e.g., a cell that is smaller than what the receive utopia interface block has been configured to handle), it will generate an interrupt to the local p, discard this ?runt? cell, and resume normal operation. the physical size of the rx fifo is sixteen cells. t he incoming data (from the receive cell processor) is written into the rx fifo, where it can be read in and processed by the atm layer processor. a fifo manager maintains the rx fifo and indicates the fifo empty and fifo full to the local p. additionally the fifo manager will indicate that atm cell data is ava ilable in the rxfifo, by as serting the rxuclav output pin. the following sections discusses each functional sub-bl ock of the receive utopia interface block in detail. additionally, these sections discuss ma ny the of the features associated with the receive utopia interface block as well as how the user can optimize these features in order to suit his/her application needs. detailed discussion of single-phy and multi-phy operation will be presented in its own sect ion even though it involves the use of all of these functional blocks.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 443 2.3.5.1 r eceive utopia b us o utput i nterface the receive utopia output interface complies with ut opia level 1, 2 and 3 standard interface (e.g., the receive utopia can support both single-phy and mu lti-phy operations). additionally, the xrt94l33 provides the user will the option of varying the following feat ures associated with the receive utopia bus interface. ? operating the receive utopia data bus per the utopia levels 1, 2 or 3 standards ? receive utopia data bus width of 8 or 16 bits. ? the cell size (e.g., the number of octets being processed per cell via the utopia bus) ? assigning a utopia address to a given sts-3c port. ? whether the receive utopia clock de-skewing pll is enabled or not. figure 112 presents a simple illustration of the receive utopia interface block, al ong with its external input pins. figure 112 a simple illustration of the receive utopia interface block a discussion of the operation of the receive utopia bus interface along with each of these options will be presented below. 2.3.5.1.1 the pins of the receive utopia bus interface the atm layer processor will interf ace to the receive utopia interf ace block via the following pins. ? rxudata[15:0] - receive ut opia data bus output pins. ? rxuaddr[4:0] - receive ut opia address bus input pins. ? rxuclk - receive utopia in terface block clock input pin. ? rxusoc - receive ?start of cell? indicator output pin. ? rxuprty - receive utopia - odd parity output pin. ? rxuenb* - receive utopia data bus - output enable input pin. ? rxuclav/rxfullb* - rxfifo cell available output pin. each of these signals is briefly discussed below. rxudata[15:0] - receive utopia data bus outputs the atm layer processor will read atm cell data from t he receive utopia interface block in a byte-wide (or 16-bit word-wide) manner, via these output pins. t he receive utopia data bus can be configured to operate in the ?8 bit wide? or ?16 bit wide? mode (see se ction _). if the ?8-bit wide? mode is selected, then only the rxudata[7:0] output pins will be active and capable of transmitting data to the atm layer processor. if the 16-bit wide mode is selected, then all 16 output pi ns (e.g., rxudata[15:0]) will be active. the receive utopia data bus is tri-stated while the active low rxuenb* (receive utopia bus - output enable) input signal is ?high?. therefore, the atm layer processor must assert this signal (e.g., toggle rxuenb* low) in order to read the atm cell data from the receive utop ia interface block. the data on the receive utopia data bus output pins are updated on the rising edge of the receive utopia inte rface block clock signal, rxuclk. rxuaddr[4:0] - receive utopia address bus inputs these input pins are used only when the xrt94l33 is opera ting in the multi-phy mode. therefore, for more information on the receive utopia a ddress bus, please see section _.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 444 rxuclk - receive utopia interfac e block - clock signal input pin the receive utopia interface block uses this signal to update the data on the receive utopia data bus. the receive utopia interface block also uses this signal to sample and latch the data on the receive utopia address bus pins (during multi-phy operation), into the receive utopia in terface block circuitry. this clock signal can run at frequencies of up to 50 mhz. rxuenb* - receive utopia data bus - output enable input the receive utopia data bus is tri-st ated while this input signal is negated. therefore, the user must assert this ?active-low? signal (toggle it ?l ow?) in order to read the byte (or wo rd) from the receive utopia interface block via the receive utopia data bus. rxuprty - receive utopia - odd parity bit output pin the receive utopia interface block will compute the odd -parity of each byte (or word) of atm cell data that it will place on the receive utopia data bus. the receive utopia data bus w ill output the value of the computed parity bit at the rxuprty output pin, whil e the corresponding byte (or word) is present on the receive utopia data bus. this feature allows the atm layer processor to perform parity checking on the data that it receives from the receive utopia interface block. rxusoc - receive utopia - ?start of cell? indicator output pin the receive utopia interface block will pulse this out put signal ?high?, for one clock period of rxuclk, when the first byte (or word) of a new cell is present on the re ceive utopia data bus. this output signal will be ?low? at all other times. rxuclav/rxemptyb* - rx fifo cell available/rxempty* this output signal is used to alert the atm layer proc essor that the rx fifo contains some atm cell data that is available for reading. please see section 7.4.2.2.1 for more information regarding this signal.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 445 configuration options with the re ceive utopia interface block selecting the utopia level the xrt94l33 permits the user to configure the receive utopia interface block in either of the following ?utopia levels?. ? utopia level 3 ? utopia level 1 or 2 the user can configure the receive utopia interf ace block (within the xrt94l33) to operate in the appropriate utopia level, by writin g the appropriate value into bit 7 (utopia level) within the ?receive utopia control register?, as depicted below. receive utopia/pos-phy control register ? byte 0 (address = 0x0503) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level 3 disable multi-phy polling enable back to back polling enable direct status indication enable receive utopia/pos-phy data bus width cell size[1:0] r/w r/w r/w r/w r/w r/w r/w r/w x 1 0 0 1 1 1 1 setting this bit-field to ?0? configures the receive utopia interface block to support ?utopia level 3? signaling. conversely, setting this bit-field to ?1? co nfigures the receive utopia interface block to support the ?utopia levels 1 and 2? form of signaling. a description of the operati on of the receive utopia interface block, for utopia level 1, 2 and 3 operation is presented below. 2.3.5.1.2 utopia level 1 and 2 operation of the receive utopia interface block this section presents an in-depth write up of the utopia level 1 and 2 protocols. when the receive utopia interface block has been conf igured to operate in the ?utopia level 2? mode, then it will either be configured to operate in the ?s ingle-phy? or ?multi-phy? mode, as described below. 2.3.5.1.2.1 selecting the utopia data bus width the user can configure the width of the receive utopia data bus to be either 8 or 16 bits by writing the appropriate data into bits 3 and 2 (receive utopia data bus width[1:0]) within the ?receive utopia control? register, as depicted below. receive utopia/pos-phy control register ? byte 0 (address = 0x0503) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level 3 disable multi-phy polling enable back to back polling enable direct status indication enable receive utopia/pos-phy data bus width cell size[1:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 0 0 x x 1 1 if the user chooses a utopia data bus width of 8 bits, then only the receive utopia data outputs: rxudata[15:8] will be active. (the output pins: rxudata[7: 0] will not be active). if the user chooses a utopia data bus width of 16 bits, then all of the re ceive utopia data outputs: rxudata[15:0] will be
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 446 active. the following table relates the value of bits 2 and 3 (receive utopia data bus width[1:0]) within the receive utopia control register, to the corres ponding width of the receive utopia data bus. note: this configuration setting does not apply to the transmi t utopia interface block. the user will still need to specify the width of the transmit utopia data bus separately, as described in section _. table 22 the relationship between the contents of ?receive utopia data bus width[1:0] within the receive utopia control register and the operating width of the receive utopia data bus r eceive utopia d ata b us w idth [1:0] w idth of r eceive utopia d ata b us 00 in-active: 01 8 bits 10 16 bits 11 not valid (do not use)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 447 selecting the cell size (number of octets per cell) the xrt94l34 device permits the user to select the number of octets per cell that the receive utopia interface block will output, following ea ch assertion of the rxusoc output pi n. specifically, the user has the following cell size options. ? if the utopia data bus width is set to 8 bits then the user can choose: 52 bytes (with no hec byte in the cell), or 53 bytes (with either a dummy or actual hec byte in the cell) ? if the utopia data bus width is set to 16 bits then the user can choose: 52 bytes (with no hec byte in the cell), or 54 bytes (with either a dummy or actual hec byte, and a stuff byte in the cell) the user makes their selection by writing the appropriate data into bits 1 and 0 (cell_size_sel[1:0]) within the receive utopia control regi ster, as depicted below. receive utopia/pos-phy control register ? byte 0 (address = 0x0503) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level 3 disable multi-phy polling enable back to back polling enable direct status indication enable receive utopia/pos-phy data bus width cell size[1:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 0 0 0 1 1 x x the following table presents the relationship between t he value of these bits and the number of octets/cell that the receive utopia in terface block will process. table 23 the relationship between the contents of bits 1 and 0 (cell_size_sel[1:0]) within the receive utopia control register, and the number of octets per cell that will be processed by the receive utopia interface blocks following each assertion of the rxusoc output pin c ell _s ize _s el [1:0] n umber of b ytes /c ells 00 52 bytes/cell 01 53 bytes/cell (only valid if the receive utopia data bus width = 8 bits) 10 54 bytes/cell 11 unused once the user has implemented his/her selection for t he cell size, then the receive utopia interface block will be configured to output ?cell size? number of octets, per each as sertion of ?rxusoc?. 2.3.5.1.2.2 cell level handshaking atm forum documentation refers to both ?cell level ? and ?octet-level? handshaking. however, the xrt94l33 only supports the ?cell-level? handshaking mode . octet-level handshaking is not supported. in the ?cell level handshaking mode, when the xrt94l33 sets the rxuclav output pin to a logic ?1?, it means that the rxfifo contains at least one atm cell?s wort h of data that needs to be read out by the atm layer processor. however, when rxuclav toggles from ?hi gh? to ?low? it indicates that the rxfifo does not contain any cells (following the one that is currently bei ng read out of the receive utopia interface block). the atm layer processor is expected to poll the stat e of the rxuclav output pin towards the end of the
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 448 reception of the cell currently being read out, and to proceed with reading out the next atm cell from the receive utopia interface only if rxuclav is at a logic ?high?. figure 113 presents a timing diagram of that illustrates the behavior of various receive utopia interface block signals, when the receive utopia interface bloc k is operating the ?cell-level? handshaking mode. figure 113 timing diagram of various receive utop ia interface block signals, when the receive utopia interface block is operating in the ?cell level handshaking? mode rxclk rxclav rxenb* rxdata[15:0] rxsoc w24 w25 w26 w0 w1 w2 w25 w26 1 2 3 4 5 6 7 8 9 31 32 34 notes: regarding figure 113: the receive utopia data bus is configured to be 16 bits wi de. hence, the data, which t he receive utopia places on the receive utopia data bus, is expressed in terms of 16 bit words: w0 - w26. the receive utopia interface block is configured to handle 54 bytes/cell. hence, figure 86 illustrates the atm layer processor reading in 27 words (w0 through w26) for each atm cell. in figure 113 the atm layer processor is just finishing up its reading of an atm cell. prior to clock edge #2, the rxfifo does not contain enough atm cell data to make up at least one cell. hence, the receive utopia interface block negates the rxuclav signal. the atm layer processor detects that the rxclav signal has toggled ?low?; at clock edge #2. hence, the atm layer processor will fini sh reading in the current atm cell; from the receive utop ia interface block of the xrt94l33 (e.g., words w25 and w26). afterwards, the atm layer processor will negate the rx uenb* signal and will cease to read in anymore atm cell data from the receive utopia interface block; until rxuclav toggles ?high? again. the rxfifo accumulates enough cell data to make up a complete atm cell shortly before clock edge #5. at this point the receive utopia interface block reflects this fact by asserting the rxuclav signal. the atm layer processor detects that the rxuclav signal has toggled ?high? at clock edge #5. consequently, the atm layer processor then asserts the rx uenb* signal (e.g., toggles it ?low?) after clock edge #5. the receive utopia interface block detects the fa ct that the rxuenb* i nput pin has been asserted at clock edge #6. the receive utopia interface block then responds to this si gnaling by placing the first word of the next cell on the receive utopia data bus. afterwards, the atm layer processor continues to read in the remaining words of this cell. 2.3.5.1.2.3 utopia modes of operati on (single phy and multi-phy operation) the xrt94l33 can be configured to support either si ngle-phy or multi-phy operation. each of these operating modes is discussed below. 2.3.5.1.2.4 single phy operation the xrt94l33 permits the user to configure it to operat e in either the ?single-phy? or ?multi-phy? mode. the user can configure the chip to operate in the ?singl e-phy? mode by setting bit 6 (multi-phy mode) to ?0?; as illustrated below. receive utopia/pos-phy control register ? byte 0 (address = 0x0503)
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 449 b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level 3 disable multi-phy polling enable back to back polling enable direct status indication enable receive utopia/pos- phy data bus width cell size[1:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 0 0 0 1 1 x x note: this configuration setting does not apply to the transmit utopia interface block. t herefore, the user will also need to configure the transmit utopia interface block in to the single-phy mode, as described in section _. in single-phy mode operation, the atm layer processor is pumping dat a into and receiving data from only one phy-layer device, as depicted below in figure 114 figure 114 simple illustration of single - phy mode operation xrt95l34 atm switch (atm layer device) txudata[15:0] rxudata[15:0] txuclav txldata_p txldata_n rxldata_p rxldata_p txflow control input to/from optical transceiver rxuclav txusoc txuenb* txuprty txuclk rxuclk rxusoc rxuenb* rxuprty rxflow control input rx start of cell input tx start of cell output rx read output enable signal tx write enable output rx utopia data bus parity tx utopia data bus parity rx fifo clock signal tx fifo clock signal rx atm cell data tx atm cell data this section presents a detailed description of the re ceive utopia interface block operating in the ?single- phy? mode. a description of the transmit utopia in terface block operating in the ?single-phy? mode is presented in section _. whenever t he receive utopia interface block ha s been configured to operate in the single-phy mode, and whenever the at m layer processor wishes to read out one or a series of atm cells from the receive utopia interface block, it must do the following. 1. check the level of the rxuclav pin if the rxuclav pin is ?high? then the rxfifo contains some atm cell data that needs to be read by the atm layer processor. in this case, the atm layer processo r should begin to read the cell data from the receive utopia interface block. however, if the rxuclav pi n is ?low?, then the rxfifo does not contain any cell data, that can be read. in this ca se, the atm layer processor should wait until rxuclav toggles ?high? before attempting to read any more cell data from the ?receive utopia interface block?.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 450 2. assert the rxuenb* pin and read the first byte (or word) of the new cell from the receive utopia data bus. once the atm layer processor has detected that rx uclav has toggled ?high?, then it should assert the rxuenb* input pin (e.g., toggling it ?low?). once the receive utopia interface bl ock has determined that the rxuenb* input pin is ?low?, then it will begin to place some cell data onto the receive utopia data bus. if this first byte (or word) is the beginning of a new atm cell, then the atm layer processor should verify that this byte (or word) is indeed the beginning of a new cell, by observing the rxusoc output pin (of the xrt94l33 ic) pulsing ?high? for one clock period of rxuclk. 3. compute the odd-parity of the byte (or word) that is being read from the receive utopia data bus, and compare the value of this parity bit with that of the rxuprty output pin. this operation is optional, but should be done concurrent ly while checking for the assertion of the rxusoc output pin. when reading in the subsequent bytes (or words) of the cell, the atm layer must do the following. ? repeat steps 1 and 2. ? the atm layer processor should check the rxuclav si gnal level just as it (the atm layer processor) is reading in the very last byte (or word) of a given cell. if the rxuclav level is ?high?, then the atm layer processor should proceed to read in the next cell from t he receive utopia interface block. however, if the rxuclav level is ?low?, then the atm layer processor should halt reading in data, when it reaches the end of the cell (that it is currently reading in). ? the atm layer processor should keep a count on t he total number of bytes that have been read in since the last assertion of the rx usoc output pin. this will help the at m layer processor to determine when it has reached the boundary of a given cell. the above-mentioned procedure is also depicted in ?f low chart form? in figure 115 and in timing diagram form in figure 116. figure 115 flow chart depicting the approach that the atm layer processor should take when reading atm cell data from the receive utopia interface, when the xrt94l33 is operating in the single-phy mode
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 451 start check the level of the rxclav pin. is rxclav ?high?? is this the first byte (word) of a new cell? is the current cell complete? is there anymore cells to read ? end assert the receive utopia interface block output enable input pin - rxenb*. read in the first byte (word) from the receive utopia data bus. read in the odd-parity value of this byte/ word from the rxpry output pin. check and verify that the rxsoc pin is asserted. perform the following, concurrently reading in the first byte/word of a cell perform the following, concurrently read in the next byte (word) from the receive utopia data bus read in the odd-parity value of this byte (word) from the rxpry output pin. assert the ?receive utopia data bus output enable input pin - rxenb*. reading in the remaining bytes/words of a cell no yes yes no no no yes yes figure 116 timing diagram of various receive utop ia interface block signals, when the receive utopia interface block is operating in the ?cell level handshaking? mode rxclk rxclav rxenb* rxdata[15:0] rxsoc w24 w25 w26 w0 w1 w2 w25 w26 1 2 3 4 5 6 7 8 9 31 32 34 notes regarding figure 116 : the receive utopia data bus is configured to be 16 bits wi de. hence, the data, which the receive utopia places on the receive utopia data bus, is expressed in terms of 16 bit words: w0 - w26. the receive utopia interface block is configured to handle 54 bytes/cell. hence, figure 86 illustrates the atm layer processor reading in 27 words (w0 through w26) for each atm cell. figure 116, the atm layer processor is just finishing up its reading of an atm cell. prior to clock edge #2, the rxfifo does not contain enough atm cell data to make up at least one cell. hence, the receive
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 452 utopia interface block negates the rxuclav signal. the atm layer processor detects that the rxclav signal has toggled ?low?; at clock edge #2. hence, the atm layer processor will fini sh reading in the current atm cell; from the receive utop ia interface block of the xrt94l33 (e.g., words w25 and w26). afterwards, the atm layer processor will negate the rx uenb* signal and will cease to read in anymore atm cell data from the receive utopia interface block; until rxuclav toggles ?high? again. the rxfifo accumulates enough cell data to make up a complete atm cell shortly before clock edge #5. at this point the receive utopia interface block reflects this fact by asserting the rxuclav signal. the atm layer processor detects that the rxuclav signal has toggled ?high? at clock edge #5. consequently, the atm layer processor then asserts the rx uenb* signal (e.g., toggles it ?low?) after clock edge #5. the receive utopia interface block detects the fa ct that the rxuenb* i nput pin has been asserted at clock edge #6. the receive utopia interface block then responds to this si gnaling by placing the first word of the next cell on the receive utopia data bus. afterwards, the atm layer processor continues to read in the remaining words of this cell. 2.3.5.1.2.5 multi-phy operation the xrt94l33 permits the user to configure it to operate in the ?multi-phy? mode. this can be accomplished by setting bit 6 (multi-phy mode), within th e ?receive utopia control register ? byte 0? to ?1? as depicted below. receive utopia/pos-phy control register ? byte 0 (address = 0x0503) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 utopia level 3 disable multi-phy polling enable back to back polling enable direct status indication enable receive utopia/pos-phy data bus width cell size[1:0] r/w r/w r/w r/w r/w r/w r/w r/w 1 1 0 0 1 1 x x note: this configuration setting does not apply to the transmit utopia interface block. t herefore, the user will also need to configure the transmit utopia interface block in to the ?multi-phy? mode, as described in section _. in the ?multi-phy? operating mode, t he atm layer processor may be writing data into and reading data from several uni (e.g., phy layer) devices in parallel. figure 114 presents an illustration of a simple ?multi-phy system? consisting of a single atm layer processor be ing interfaced to two (2) uni devices. when the xrt94l33 is operating in the multi-phy mode, the receiv e utopia interface block will support two kinds of operations with the atm layer processor. ? polling for uni (phy layer) devices that contain atm cell waiting to be read. ? selecting which uni (out of several possible uni devices) to read atm cell data from. each of these operations is discussed in the sections below. however, prior to discussing each of these operations, the reader must understand the following. ?multi-phy? operation involves the use of one (1) atm layer processor and several uni (or phy-layer) devices, within a system. the atm layer processor is expected to read/write atm cell data from/to these uni devices. hence, ?multi-phy? operation requires , at a minimum, some means for the atm layer processor to uniquely identify a particular uni device (among all of the uni devices within the ?multi-phy? system) that it wishes to ?poll?, write atm cell data to, or read atm cell data from. actually, ?multi-phy? operation provides an addressing scheme allows th e atm layer processor to uniquely identify ?utopia interface blocks? (e.g., transmit and receive) within all of the uni devices, oper ating in the ?multi-phy? system. in order to uniquely identify a given ?utopia interface block?, within a ?multi-phy? system, each ?transmit and receive utopia interface blocks are a ssigned a 5-bit ?utopia address? value. the user assigns this address value to a particular ?receive utopia interface block? by writing this address value into
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 453 the ?receive utopia address register? (address = 0x0513) and appropriate data into the ?receive utopia port address? register (address = 0x0517); within it s ?host? xrt94l33; per the procedure (as presented below). the bit-format of the ?receive utopia addres s register? and ?receive port address? register is presented below. receive utopia address register (address = 0x0513) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused rx_utopia_addr[4:0] ro ro ro r/w r/w r/w r/w r/w 0 0 0 x x x x x
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 454 receive utopia port number register (address = 0x0517) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused rx_utopia_port_number[4:0] r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 x x x x x 2.3.5.1.2.6 assigning r eceive utopia addresses to each sts-3c channel within the xrt94l33 the xrt94l33 can be configured to function as a four channel atm uni over either an sts-3 or an sts-3c signal. as a consequence, for multi-phy operatio n, the xrt94l33 can be assigned as many as three ?receive utopia addresses? at a gi ven time (one for each sts-1 channel). the user can assign a ?receive utopia address? value to a given channel, within the xrt94l33 by executing the following steps. step 1 ? assign a ?receive utopia address? to channel 0 the user can accomplish this by doing the following. step 1a ? set bits 0 through 4 (?rx_utopia_port_number[4:0]?) within the ?receive utopia port number register? to ?0x00?; as depicted below. receive utopia port number register (address = 0x0517) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused rx_utopia_port_number[4:0] r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 0 this step configures an internal ?receive utopia a ddress assignment? pointer to point to ?sts-3c channel 0? within the xrt94l33. step 1b ? set bits 0 through 4 (?rx_utopia_addr[4:0]?) within the ?receive utopia address? register to the desired ?multi-phy? address value for this channel [a4, a3, a2, a1, a0]; as depicted below. receive utopia address register (address = 0x0513) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused rx_utopia_addr[4:0] ro ro ro r/w r/w r/w r/w r/w 0 0 0 a4 a3 a2 a1 a0 this step configures the receive utopia address, of the value [a4, a3, a2, a1, a0] to be assigned to channel 0. notes: during this step, the user can write in any value, between 0x00 and 0x1e, prov ided this ?multi-phy address? is unique among all of the receive ut opia interface addresses wi thin a ?multi-phy? system. use of the value ?0x1f? is not permitted. these steps do not assign a transmit utopia address value to the sts-3c channel 0. this assignment must be performed separately per the ?transmi t utopia address? assignment inst ructions, presented in section _.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 455 once the user has executed steps 1a and 1b, then st s-3c channel 0 (within the xrt94l33) has been assigned the ?transmit utopia addr ess? of [a4, a3, a2, a1, a0]. step 2 ? assign a ?receive utopia address? to sts-3c channel 1 the user can accomplish this by doing the following. step 2a ? set bits 0 through 4 (?rx_utopia_port_number[4:0]?) within the ?receive utopia port number register? to ?0x01?; as depicted below. receive utopia port number register (address = 0x0517) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused rx_utopia_port_number[4:0] r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0 0 0 0 1 this step configures an internal ?receive utopia a ddress assignment? pointer to point to ?sts-3c channel 1? within the xrt94l33. step 2b ? set bits 0 through 4 (?rx_utopia_addr[4:0]?) within the ?receive utopia address? register to the desired ?multi-phy? address value for this channel [b4, b3, b2, b1, b0]; as depicted below. receive utopia address register (address = 0x0513) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused rx_utopia_addr[4:0] ro ro ro r/w r/w r/w r/w r/w 0 0 0 b4 b3 b2 b1 b0 this step configures the receive utopia address, of the value [b4, b3, b2, b1, b0] to be assigned to channel 1. notes: during this step, the user can write in any value, between 0x00 and 0x1e, prov ided this ?multi-phy address? is unique among all of the receive utopia addresses within a ?multi-phy? system. use of the value ?0x1f? is not permitted. these steps do not assign a transmit utopia address value to sts-3c channel 1. this assignment must be performed separately per the ?transmit utopia address assi gnment? instructions pr esented in section _. once the user has executed steps 2a and 2b, then st s-3c channel 1 (within the xrt94l33) has been assigned the ?receive utopia addr ess? of [b4, b3, b2, b1, b0]. step 3 ? assign a ?receive utopia address? to sts-3c channel 2 the user can accomplish this by doing the following. step 3a ? set bits 0 through 4 (?rx_utopia_port_number[4:0]?) within the ?receive utopia port number register? to ?0x02?; as depicted below. receive utopia port number register (address = 0x0517) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused rx_utopia_port_number[4:0] r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0 0 0 1 0
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 456 this step configures an internal ?receive utopia a ddress assignment? pointer to point to ?sts-3c channel 2? within the xrt94l33. step 3b ? set bits 0 through 4 (?rx_utopia_addr[4:0]?) within the ?receive utopia address? register to the desired ?multi-phy? address value for this channel [c4, c3, c2, c1, c0]; as depicted below. receive utopia address register (address = 0x0513) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused rx_utopia_addr[4:0] ro ro ro r/w r/w r/w r/w r/w 0 0 0 c4 c3 c2 c1 c0 this step configures the receive utop ia address, of the value [c4, c3, c2, c1, c0] to be assigned to sts- 3c channel 2. notes: during this step, the user can write in any value, betw een 0x00 and 0x1e, provided this ?multi-phy address? is unique among all of the receive utopia interface addresses within a ?multi-phy? system. use of the value ?0x1f? is not permitted. these steps do not assign a transmit utopia address value to sts-3c channel 2. this assignment must be performed separately per the ?transmit utopia address assi gnment? instructions pr esented in section _. once the user has executed steps 3a and 3b then st s-3c channel 2 (within the xrt94l33) has been assigned the ?receive utopia address? of [c4, c3, c2, c1, c0]. step 4 ? assign a ?receive utopia address? to sts-3c channel 3 the user can accomplish this by doing the following. step 4a ? set bits 0 through 4 (?rx_utopia_port_number[4:0]?) within the ?receive utopia port number register? to ?0x03?; as depicted below. receive utopia port number register (address = 0x0517) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused rx_utopia_port_number[4:0] r/o r/o r/o r/w r/w r/w r/w r/w 0 0 0 0 0 0 1 1 this step configures an internal ?receive utopia a ddress assignment? pointer to point to ?sts-3c channel 3? within the xrt94l33. step 4b ? set bits 0 through 4 (?rx_utopia_addr[4:0]?) within the ?receive utopia address? register to the ?multi-phy? address value for this channel [d4, d3, d2, d1, d0]; as depicted below. receive utopia address register (address = 0x0513) b it 7 b it 6 b it 5 b it 4 b it 3 b it 2 b it 1 b it 0 unused rx_utopia_addr[4:0] ro ro ro r/w r/w r/w r/w r/w 0 0 0 d4 d3 d2 d1 d0 this step configures the receive utop ia address, of the value [d4, d3, d2, d1, d0] to be assigned to sts- 3c channel 3.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 457 notes: during this step, the user can write in any value, between 0x00 and 0x1e prov ided this ?multi-phy address? is unique among all of the receive ut opia interface addresses wi thin a ?multi-phy? system. use of the value ?0x1f? is not permitted. these steps do not assign a transmit utopia address value to sts-3c channel 3. this assignment must be performed separately per the ?transmit utopia address assi gnment? instructions pr esented in section _. once the user has executed steps 4a and 4b then st s-3c channel 3 (within the xrt94l33) has been assigned the ?receive utopia addr ess? of [d4, d3, d2, d1, d0]. 2.3.5.1.2.7 atm layer processor ?polling? of the unis, in the multi-phy mode in this section, the various multi-ph y operations (e.g., polling and selection for writing) will be first discussed for a ?conceptual multi-phy? system, and then later, sp ecifically for the xrt94l33. when the xrt94l33 is operating in the ?multi-phy? mode, then the receive ut opia interface block will automatically be configured to support ?polling?. ?polling? allows an atm layer pr ocessor (which is interfaced to several uni devices) to determine which unis are capable of receiving and handlin g additional atm cell data, at any given time. the manner in which the atm layer processor ?polls? its un i devices, (per the ?conceptual multi-phy? system) follows. figure 117 an illustration of the ?conceptual mult i-phy system consisting of uni devices #1 and #2 txudata[15:0] txuaddr[4:0] txuprty txuenb* txusoc txuclav rxudata[15:0] rxuaddr[4:0] rxuprty rxuenb* rxusoc rxuclav uni # 1 txaddr = 0x00 rxaddr = 0x01 txudata[15:0] txuaddr[4:0] txuprty txuenb* txusoc txuclav rxudata[15:0] rxuaddr[4:0] rxuprty rxuenb* rxusoc rxuclav txaddr = 0x02 rxaddr = 0x03 txdata[15:0] ut_addr[4:0] tx_parity tx_ut_wr* tx_soc_out txclav_in rxdata[15:0] rx_parity rx_ut_rd* rx_soc_in rxclav_in atm layer processor uni # 2
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 458 2.3.5.1.2.8 atm layer processor ?polling? in a conceptual multi-phy system figure 117depicts a ?multi-phy? system consisting of a single atm layer processor and two (2) uni devices, which are designated as ?uni #1? and ?u ni #2?. in this figure, both of the unis are connected to the atm layer processor via a common ?transmit utopia? da ta bus, a common ?receive utopia? data bus, a common ?txuclav? line, a common ?rxuclav? line, as well as common txuenb*, rxuenb*, txusoc and rxusoc lines. the atm layer processor will also be addressing both the transmit and receive utopia interface blocks via a common ?utopia? address bus (u t_addr[4:0]) therefore, the transmit and receive utopia interface blocks, within a given uni might have different addresses; as depicted in figure 117. the utopia address values, that have been assigned to each of the transmit and receive utopia interface blocks, within figure 26, are listed below in table 24. table 24 utopia address values of the utopia interface blocks illustrated in figure 117. b lock utopia a ddress v alue transmit utopia interface block - uni #1 0x00 receive utopia interface block - uni #1 0x01 transmit utopia interface block - uni #2 0x02 receive utopia interface block - uni #2 0x03 recall, that the receive utopia interface blocks were assigned these addresses by writing these values into registers that are similar to the ?receive utopia po rt number (address = 0x0517) and the receive utopia address register? (address = 0x0513) within these uni devices. the discussion of the transmit utopia interface blocks, within unis #1 and #2 is presented in section _. polling operation consider that the atm layer processor is currently reading a continuous stream of atm cell data from uni #1. while reading this atm cell data from uni #1, the atm layer processor can also ?poll? uni #2 for ?availability? (e.g., tries to determine if uni # 2 contains any atm cells, within its rxfifo, that needs to be read out via its receive utopia interface block). the atm layer processor?s role in the ?polling? operation the atm layer processor accomplishes this ?po lling? operation by executing the following steps. 1. assert the rxuenb* input pin (if it is not asserted already). the uni device (being ?polled?) will know that this is only a ?polling? operation, if the rxuenb* input pin is asserted, prior to detecting its utopia address on the ?utopia address? bus (rxuaddr[4:0]). 2. the atm layer processor places the address of the receive utopia interface block of uni #2 onto the utopia address bus, ut_addr[4:0], 3. the atm layer processor will then check th e value of its ?rxucl av_in? input pin (see figure 117 ). the atm layer processor is suppose to check the stat e of the ?rxuclav? signal, one ?rxuclk? period after placing the utopia address (corresponding to a particular uni device) on the ?rxuaddr[4:0]? input pins. if ?rxuclav? is sampled ?high? then this means that this particular uni device contains at least one atm cell of data (within its rxfifo) that needs to be read out by the atm layer processor. conversely, if rxuclav is sampled ?low? then this means that this particular un i device does not contain at least one atm cell of data within its rxfifo, that needs to be r ead out via the atm layer processor. the uni devices role in the ?polling? operation uni #2 will sample the signal levels pl aced on its rx utopia address input pins (rxua ddr[4:0]) on the rising edge of its ?receive utopia interfac e block? clock input signal, rxuclk. afterwards, uni #2 will compare the
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 459 value of these ?receive utopia address bus input pin? signals with that of the contents of its ?rx utopia address register (address = 0x0513). if these values do not match, (e.g., rxuaddr[4:0] 0x03) then uni #2 will keep its ?rxuclav? output signal ?tri-stated?; and will continue to sample its ?receive utopia a ddress bus input? pins; with each rising edge of rxuclk. if these two values do match, (e.g., rxuaddr[4:0] = 0x 03) then uni #2 will drive its ?rxuclav? output pin to the appropriate level, reflecting its rxfifo ?fill-status?. since the uni is only operating in the ?cell level handshaking? mode, the uni will drive the rxuclav output signal ?high? if it contains at least one complete atm cell of data within its rxfifo, that needs to be r ead out by the atm layer proc essor. conversely, the uni will drive the ?rxuclav? output sig nal ?low? if its rxfifo contains less than one complete atm cell of data. when uni #2 has been selected for ?polling?, uni #1 w ill continue to keeps its ?r xuclav? output signal ?tri- stated?. therefore, when uni #2 is dr iving its ?rxuclav? output pin to the ap propriate level; it will be driving the entire ?rxuclav? line, within the ?multi-phy? sys tem. consequently, uni#2 will also be driving the ?rxuclav_in? input pin of the atm lay er processor (see figure 117). if uni #2 drives the ?rxuclav? line ?low?, upon the appl ication of its address on t he utopia address bus, then the atm layer processor will ?learn? that there are no atm cells of data (within the rxfifo of uni # 2) that need to be read out via the ?receive utopia interface? block. howe ver, if uni #2 drives the rxuclav line ?high? (during ?polling?), then the atm layer proces sor will know that uni # 2 does contain at least one atm cell of data (within its rxfifo) that needs to be read out via the receive utop ia interface block. figure 118presents a timing diagram, that depicts the behavior of the atm layer processor?s and the uni?s signals during polling. figure 118 timing diagram illustrating the behavior of various signals from the atm layer processor and the uni, during polling rxuclk rxuaddr[4:0] rxuclav rxuenb* rxudata[15:0] rxusoc 01h 1fh 03h 1fh 01h 03h 1fh 03h 01h 1fh 01h 03h w27 w0 w1 w2 w3 w4 w5 w6 w7 w8 w9 w10 01h 03h 01h 03h 03h 01h 01h 1 2 3 4 5 6 7 8 9 10 11 12 notes regarding figure 118 the receive utopia data bus is configured to be 16 bits wide. hence, the data, which t he atm layer processor places on the receive utopia data bus, is expressed in terms of 16 bit words: (e.g., w0 - w26). the receive utopia interface block is configured to handle 54 bytes/cell. hence, figure 92 illustrates the atm layer processor reading 27 words (w0 through w26) for each atm cell. the atm layer processor is currently reading atm cell data from the receive utopia inte rface block, within uni #1 (rxaddr[4:0] = 0x01) during this ?polling process?. the rxfifo, within uni#2?s receive utopia interface block (r xaddr[4:0] = 0x03) is either depleted or does not contain enough data to constitute a complete atm cell. hence, the rxuclav line will be driven ?low? whenever this particular receive utopia interface block is ?polled?. the receive utopia address of 0x1f is not associated with any uni device, within this ?multi-phy? system. hence, the rxuclav line is tri-stated whenever this address is ?polled?.
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 460 although figure 118 depicts connections between the trans mit utopia interface block pins and the atm layer processor; the transmit utopia interface operation, in the multi-ph y mode, will not be discussed in this section. please see section _ for a discussion on the transmit utopia interface block during multi-phy operation. 2.3.5.1.2.9 atm layer processor ?polling? with the xrt94l33 in figure 117, a simple illustration of the ?conceptual multi-phy? system consisting of two single-channel uni devices was presented. in reality, a given multi-phy system can or will consist of numerous ?multi-channel? uni devices. the xrt94l33 is an example of this, being a ?4-channel? uni device. therefore, the xrt94l33 can be thought of as consisting of four atm unis within a single package (one for each sts-3c port within the device). it is important to note that although the xrt94l33 consists of a single ?receive utop ia interface? block, the xrt94l33 can be assigned four unique (4) transmit utopia addresses as presented in section _. 2.3.5.1.2.10 reading atm cell data from a different uni after the atm layer processor has ?polled? each of the uni devices, within its system, it must now select a uni, and begin reading atm cell data from that device. the atm layer processor makes its selection and begins the reading process by: 1. applying the utopia address of the ?t arget? uni on the ?utopia address bus?. 2. negate the rxuenb* signal. this step causes the ? addressed? uni to recognize that it has been selected to transmit the next set of atm cell data to the atm layer processor. 3. assert the rxuenb* signal. 4. check and insure that the rxusoc output pin (of the selected uni) pulses ?high? when the first byte or word of atm cell data has been placed on the receive utopia data bus. 5. begin reading the atm cell data in a byte-wide (or word-wide) manner from the receive utopia data bus. figure 119 presents a flow-chart that depicts the ?uni device selecti on and read? process in multi-phy operation. figure 119 flow-chart of the ?uni device selection and read procedure? for the multi-phy operation
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 461 start poll all unis within the ?multi-phy? system. determine which unis contain atm cell data that needs to be read.? select ?available? uni 1. apply utopia address of the ?selected? receive utopia interface block onto the ?utopia address? bus. 2. negate the rxuenb* signal begin reading atm cell data into ?selected? uni 1. assert rxuenb* 2. read in the first byte/word of atm cell from the ?receive utopia data bus & check for the asserted rxusoc signal. continue to read in atm cell data check the rxuclav level while reading in the last byte (word) of the current cell.. is rxuclav ?high? ? wait for rxuclav to toggle ?high? is rxuclav ?high? ? does the atm layer processor wish to read more cells from the ?selected? uni? yes no yes yes no no figure 120 presents a timing diagram that illustrates the behavior of va rious ?receive utopia interface block? signals, during the ?multi-phy? un i device selection and read operation. figure 120 timing diagram of the receive utopia da ta and address bus signals, during the ?multi- phy? uni device selection and write operations rxuclk rxuaddr[4:0] rxuclav rxuenb* rxudata[15:0] rxusoc 01h 1fh 03h 1fh 01h 03h 1fh 01h 03h 1fh 03h 01h w0 w1 w2 w3 w4 w5 w6 w26 w25 w24 w23 cell received from 03h cell received from 01h 01h 03h 01h 03h 01h 03h 03h 1 2 3 4 5 6 7 8 9 10 11 12 notes regarding figure 120 : the receive utopia data bus is configured to be 16 bits wide. hence, the data, which the receive utopia interface block places on the receive utopia data bus, is expressed in terms of 16-bit words (e.g., w0 - w26). the receive utopia interface block is configured to handle 54 bytes/cell. hence, figure 94 illustrates the atm layer processor reading 27 words (e.g., w0 through w26) for each atm cell. in figure 120, the atm layer processo r is initially reading atm cell data from the receive utopia interface within uni #2 (rxuaddr[4:0] = 0x03). however, the atm layer processor is also polling the receive utopia interface block within uni #1 (rxuaddr[4 :0] = 0x01) and some ?non-existent? device at rxuaddr[4:0] = 0x1f. the atm layer processor complete s its reading of the cell from uni #1 at clock edge
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 462 #4. afterwards, the atm layer will cease to read any more cell data from uni #1, and will begin to read some cell data from uni #2 (rxuaddr [4:0] = 0x03). the atm layer proces sor will indicates its intention to select a new uni device for reading by negating the rxen b* signal, at clock edge #5 (see the shaded portion of figure 120). at this time , uni #1 will notice two things: 1. the utopia address for the receive utopia inte rface block, within uni #1 is on the receive utopia address bus (rxuaddr[4:0] = 0x01). 2. the rxuenb* signal has been negated. uni #1 will interpret this signaling as an indication t hat the atm layer processor is going to be performing read operations from it. afterw ards, the atm layer proc essor will begin to read atm cell data from the receive utopia interface block, within uni #1.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 463 3.0 ppp applications 3.1 transmit direction 3.1.1 transmit pos-phy interface block 3.1.2 transmit ppp packet processor block 3.2 receive direction 3.2.1 receive ppp packet processor block 3.2.2 receive pos-phy interface block 4.0 the clock synthesizer block 5.0 using the sts-3 telecom bus interface 6.0 using the sts-3 pecl interface 6.1 interfacing the xrt94l33 to an optical transceiver 6.2 interfacing the xrt94l33 to a high-speed back-p lane interface 7.0 automatic protection switchi ng within the xrt94l33 device
xrt94l33 xr rev.1.2.0. 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet 464 package outline drawing 504 tape ball grid array (35 mm x 35 mm - tbga) bottom view (a1 corner feature is mfgr option) symbol min max min max a 0.051 0.067 1.30 1.70 a1 0.020 0.028 0.50 0.70 a2 0.031 0.039 0.80 1.00 d 1.370 1.386 34.80 35.20 d1 1.300 bsc 33.02 bsc b 0.024 0.035 0.60 0.90 e 0.050 bsc 1.27 bsc p 0.006 0.012 0.15 0.30 inches millimeters note: the control dimension is in millimeter.
xr xrt94l33 3-channel ds3/e3/sts-1 to st s-3/stm-1 mapper ic data sheet rev.1.2.0. 465 notes: notice exar corporation reserves the right to make changes to th e products contained in th is publication in order to improve design, performance or reli ability. exar corporation assumes no responsibility for the use of any circuits described herein, conveys no license under any patent or other right, and makes no representation that the circuits are free of patent infringement. ch arts and schedules contained here in are only for illustration purposes and may vary depending upon a user?s specific application. while the information in this publication has been carefully checked; no responsi bility, however, is assumed for inaccuracies. exar corporation does not re commend the use of any of its products in life suppo rt applications where the failure or malfunction of the product can reasonably be expected to cause failure of the life support system or to significantly affect its safety or effectiveness. products are not autho rized for use in such applications unless exar corporation receives, in writ ing, assurances to its satisfaction that: (a) the risk of injury or damage has been minimized; (b) the user assumes all such risks; (c) potential liabilit y of exar corporation is adequately protected under the circumstances. copyright 2003 exar corporation datasheet november 2006

▲Up To Search▲

Price & Availability of XRT94L33IB

	To Download XRT94L33IB Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .